diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 23b8c8299..b4fb205cd 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-11 16:10+0000\n" +"POT-Creation-Date: 2023-10-09 08:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -231,7 +231,7 @@ msgstr "" #: ../../content/administration/install/deploy.rst:46 #: ../../content/administration/install/deploy.rst:58 #: ../../content/administration/install/deploy.rst:153 -#: ../../content/administration/install/deploy.rst:276 +#: ../../content/administration/install/deploy.rst:280 msgid "in :ref:`the configuration file ` set:" msgstr "" @@ -266,8 +266,8 @@ msgstr "" #: ../../content/administration/install/deploy.rst:95 #: ../../content/administration/install/deploy.rst:145 -#: ../../content/administration/install/deploy.rst:231 -#: ../../content/administration/install/deploy.rst:271 +#: ../../content/administration/install/deploy.rst:235 +#: ../../content/administration/install/deploy.rst:275 msgid "Configuration sample" msgstr "" @@ -352,299 +352,279 @@ msgid "Builtin server" msgstr "" #: ../../content/administration/install/deploy.rst:182 -msgid "Odoo includes built-in HTTP servers, using either multithreading or multiprocessing." +msgid "Odoo includes built-in HTTP, cron, and live-chat servers, using either multi-threading or multi-processing." msgstr "" #: ../../content/administration/install/deploy.rst:185 -msgid "For production use, it is recommended to use the multiprocessing server as it increases stability, makes somewhat better use of computing resources and can be better monitored and resource-restricted." +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-running requests such as long polling. 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/install/deploy.rst:189 -msgid "Multiprocessing is enabled by configuring :option:`a non-zero number of worker processes `, the number of workers should be based on the number of cores in the machine (possibly with some room for cron workers depending on how much cron work is predicted)" +#: ../../content/administration/install/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/install/deploy.rst:193 -msgid "Worker limits can be configured based on the hardware configuration to avoid resources exhaustion" -msgstr "" - -#: ../../content/administration/install/deploy.rst:196 -msgid "multiprocessing mode currently isn't available on Windows" -msgstr "" - -#: ../../content/administration/install/deploy.rst:199 -msgid "Worker number calculation" +#: ../../content/administration/install/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/install/deploy.rst:201 -msgid "Rule of thumb : (#CPU * 2) + 1" +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/install/deploy.rst:202 -msgid "Cron workers need CPU" -msgstr "" - -#: ../../content/administration/install/deploy.rst:203 -msgid "1 worker ~= 6 concurrent users" -msgstr "" - -#: ../../content/administration/install/deploy.rst:206 -msgid "memory size calculation" -msgstr "" - -#: ../../content/administration/install/deploy.rst:208 -msgid "We consider 20% of the requests are heavy requests, while 80% are simpler ones" +#: ../../content/administration/install/deploy.rst:205 +msgid "Because it is highly customized for Linux servers, the multi-processing server is not available on Windows." msgstr "" #: ../../content/administration/install/deploy.rst:209 -msgid "A heavy worker, when all computed field are well designed, SQL requests are well designed, ... is estimated to consume around 1GB of RAM" +msgid "Worker number calculation" msgstr "" -#: ../../content/administration/install/deploy.rst:210 -msgid "A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM" +#: ../../content/administration/install/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" msgstr "" #: ../../content/administration/install/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/install/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/install/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/install/deploy.rst:218 +msgid "We consider 20% of the requests are heavy requests, while 80% are simpler ones" +msgstr "" + +#: ../../content/administration/install/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/install/deploy.rst:220 +msgid "A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM" +msgstr "" + +#: ../../content/administration/install/deploy.rst:222 msgid "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) + (heavy_worker_ratio * heavy_worker_ram_estimation) )" msgstr "" -#: ../../content/administration/install/deploy.rst:215 -#: ../../content/administration/install/deploy.rst:369 +#: ../../content/administration/install/deploy.rst:225 +#: ../../content/administration/install/deploy.rst:373 msgid "LiveChat" msgstr "" -#: ../../content/administration/install/deploy.rst:217 -msgid "In multiprocessing, a dedicated LiveChat worker is automatically started and listening on :option:`the longpolling port ` but the client will not connect to it." -msgstr "" - -#: ../../content/administration/install/deploy.rst:221 -msgid "Instead you must have a proxy redirecting requests whose URL starts with ``/longpolling/`` to the longpolling port. Other request should be proxied to the :option:`normal HTTP port `" -msgstr "" - -#: ../../content/administration/install/deploy.rst:225 -msgid "To achieve such a thing, you'll need to deploy a reverse proxy in front of Odoo, like nginx or apache. When doing so, you'll need to forward some more http Headers to Odoo, and activate the proxy_mode in Odoo configuration to have Odoo read those headers." -msgstr "" - -#: ../../content/administration/install/deploy.rst:233 -msgid "Server with 4 CPU, 8 Thread" -msgstr "" - -#: ../../content/administration/install/deploy.rst:234 -msgid "60 concurrent users" -msgstr "" - -#: ../../content/administration/install/deploy.rst:236 -msgid "60 users / 6 = 10 <- theoretical number of worker needed" +#: ../../content/administration/install/deploy.rst:227 +msgid "In multi-processing, a dedicated LiveChat worker is automatically started and listens on the :option:`--longpolling-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 ``/longpolling`` 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/install/deploy.rst:237 -msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgid "Server with 4 CPU, 8 Thread" msgstr "" #: ../../content/administration/install/deploy.rst:238 -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 ." +msgid "60 concurrent users" msgstr "" -#: ../../content/administration/install/deploy.rst:239 -msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" +#: ../../content/administration/install/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" msgstr "" #: ../../content/administration/install/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/install/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/install/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" +msgstr "" + +#: ../../content/administration/install/deploy.rst:245 msgid "in :ref:`the configuration file `:" msgstr "" -#: ../../content/administration/install/deploy.rst:257 +#: ../../content/administration/install/deploy.rst:261 msgid "HTTPS" msgstr "" -#: ../../content/administration/install/deploy.rst:259 +#: ../../content/administration/install/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/install/deploy.rst:264 +#: ../../content/administration/install/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/install/deploy.rst:265 +#: ../../content/administration/install/deploy.rst:269 msgid "Set up the SSL termination proxy (`Nginx termination example`_)" msgstr "" -#: ../../content/administration/install/deploy.rst:266 +#: ../../content/administration/install/deploy.rst:270 msgid "Set up the proxying itself (`Nginx proxying example`_)" msgstr "" -#: ../../content/administration/install/deploy.rst:267 +#: ../../content/administration/install/deploy.rst:271 msgid "Your SSL termination proxy should also automatically redirect non-secure connections to the secure port" msgstr "" -#: ../../content/administration/install/deploy.rst:273 +#: ../../content/administration/install/deploy.rst:277 msgid "Redirect http requests to https" msgstr "" -#: ../../content/administration/install/deploy.rst:274 +#: ../../content/administration/install/deploy.rst:278 msgid "Proxy requests to odoo" msgstr "" -#: ../../content/administration/install/deploy.rst:282 +#: ../../content/administration/install/deploy.rst:286 msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" msgstr "" -#: ../../content/administration/install/deploy.rst:343 +#: ../../content/administration/install/deploy.rst:347 msgid "Odoo as a WSGI Application" msgstr "" -#: ../../content/administration/install/deploy.rst:345 +#: ../../content/administration/install/deploy.rst:349 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/install/deploy.rst:351 +#: ../../content/administration/install/deploy.rst:355 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/install/deploy.rst:356 +#: ../../content/administration/install/deploy.rst:360 msgid "Cron Workers" msgstr "" -#: ../../content/administration/install/deploy.rst:358 -msgid "To run cron jobs for an Odoo deployment as a WSGI application requires" +#: ../../content/administration/install/deploy.rst:362 +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/install/deploy.rst:360 -msgid "A classical Odoo (run via ``odoo-bin``)" +#: ../../content/administration/install/deploy.rst:367 +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/install/deploy.rst:361 -msgid "Connected to the database in which cron jobs have to be run (via :option:`odoo-bin -d`)" -msgstr "" - -#: ../../content/administration/install/deploy.rst:363 -msgid "Which should not be exposed to the network. To ensure cron runners are not network-accessible, it is possible to disable the built-in HTTP server entirely with :option:`odoo-bin --no-http` or setting ``http_enable = False`` in the configuration file" -msgstr "" - -#: ../../content/administration/install/deploy.rst:371 -msgid "The second problematic subsystem for WSGI deployments is the LiveChat: where most HTTP connections are relatively short and quickly free up their worker process for the next request, LiveChat require a long-lived connection for each client in order to implement near-real-time notifications." -msgstr "" - -#: ../../content/administration/install/deploy.rst:376 -msgid "This is in conflict with the process-based worker model, as it will tie up worker processes and prevent new users from accessing the system. However, those long-lived connections do very little and mostly stay parked waiting for notifications." +#: ../../content/administration/install/deploy.rst:375 +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 HTTP requests but doesn't need a lot of processing power. All requests whose path starts with ``/longpolling`` should be directed to that server. A regular (thread/process-based) WSGI server should be used for all other requests." msgstr "" #: ../../content/administration/install/deploy.rst:381 -msgid "The solutions to support livechat/motifications in a WSGI application are:" +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 ``/longpolling`` are directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--longpolling-port ` (multi-processing server)." msgstr "" -#: ../../content/administration/install/deploy.rst:383 -msgid "Deploy a threaded version of Odoo (instead of a process-based preforking one) and redirect only requests to URLs starting with ``/longpolling/`` to that Odoo, this is the simplest and the longpolling URL can double up as the cron instance." -msgstr "" - -#: ../../content/administration/install/deploy.rst:387 -msgid "Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting with ``/longpolling/`` to :option:`the longpolling port `." -msgstr "" - -#: ../../content/administration/install/deploy.rst:392 +#: ../../content/administration/install/deploy.rst:388 msgid "Serving Static Files" msgstr "" -#: ../../content/administration/install/deploy.rst:394 +#: ../../content/administration/install/deploy.rst:390 msgid "For development convenience, Odoo directly serves all static files 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/install/deploy.rst:398 +#: ../../content/administration/install/deploy.rst:394 msgid "Odoo static files live in each module's ``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/install/deploy.rst:402 +#: ../../content/administration/install/deploy.rst:398 #: ../../content/administration/upgrade.rst:122 msgid "Todo" msgstr "" -#: ../../content/administration/install/deploy.rst:402 +#: ../../content/administration/install/deploy.rst:398 msgid "test whether it would be interesting to serve filestored attachments via this, and how (e.g. possibility of mapping ir.attachment id to filestore hash in the database?)" msgstr "" -#: ../../content/administration/install/deploy.rst:409 +#: ../../content/administration/install/deploy.rst:405 msgid "Security" msgstr "" -#: ../../content/administration/install/deploy.rst:411 +#: ../../content/administration/install/deploy.rst:407 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/install/deploy.rst:415 +#: ../../content/administration/install/deploy.rst:411 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/install/deploy.rst:421 +#: ../../content/administration/install/deploy.rst:417 msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:" msgstr "" -#: ../../content/administration/install/deploy.rst:424 +#: ../../content/administration/install/deploy.rst:420 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/install/deploy.rst:427 +#: ../../content/administration/install/deploy.rst:423 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/install/deploy.rst:432 +#: ../../content/administration/install/deploy.rst:428 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/install/deploy.rst:436 +#: ../../content/administration/install/deploy.rst:432 msgid "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. 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/install/deploy.rst:443 +#: ../../content/administration/install/deploy.rst:439 msgid "Once your ``db_name`` and ``db_filter`` 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/install/deploy.rst:449 +#: ../../content/administration/install/deploy.rst:445 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/install/deploy.rst:454 +#: ../../content/administration/install/deploy.rst:450 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/install/deploy.rst:458 +#: ../../content/administration/install/deploy.rst:454 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/install/deploy.rst:461 +#: ../../content/administration/install/deploy.rst:457 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/install/deploy.rst:468 +#: ../../content/administration/install/deploy.rst:464 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/install/deploy.rst:474 +#: ../../content/administration/install/deploy.rst:470 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/install/deploy.rst:478 +#: ../../content/administration/install/deploy.rst:474 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/install/deploy.rst:482 +#: ../../content/administration/install/deploy.rst:478 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/install/deploy.rst:486 +#: ../../content/administration/install/deploy.rst:482 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/install/deploy.rst:497 +#: ../../content/administration/install/deploy.rst:493 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/install/deploy.rst:508 +#: ../../content/administration/install/deploy.rst:504 msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques." msgstr "" -#: ../../content/administration/install/deploy.rst:511 +#: ../../content/administration/install/deploy.rst:507 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/install/deploy.rst:510 +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/install/deploy.rst:518 msgid "Blocking Brute Force Attacks" msgstr "" @@ -1007,27 +987,31 @@ msgstr "" msgid "Windows" msgstr "" -#: ../../content/administration/install/packages.rst:150 +#: ../../content/administration/install/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/install/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/install/packages.rst:153 +#: ../../content/administration/install/packages.rst:158 msgid "Execute the downloaded file." msgstr "" -#: ../../content/administration/install/packages.rst:156 +#: ../../content/administration/install/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/install/packages.rst:159 +#: ../../content/administration/install/packages.rst:164 msgid "Accept the `UAC `_ prompt." msgstr "" -#: ../../content/administration/install/packages.rst:160 +#: ../../content/administration/install/packages.rst:165 msgid "Go through the installation steps." msgstr "" -#: ../../content/administration/install/packages.rst:162 +#: ../../content/administration/install/packages.rst:167 msgid "Odoo launches automatically at the end of the installation." msgstr "" @@ -1602,32 +1586,144 @@ msgstr "" msgid "Finally, click :guilabel:`Test Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Microsoft Outlook using OAuth authentication." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:192 -msgid "Multiple user configuration" -msgstr "" - #: ../../content/administration/maintain/azure_oauth.rst:194 -msgid "Each user should have a separate server set up. The :guilabel:`from-filter` should be set so that only the user's email is sent from that server. In other words, only a user with an email address that matches the set :guilabel:`from-filter` is able to use this server." +msgid "Configuration with a single outgoing mail server" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:198 -msgid "After setting the :guilabel:`from-filter`, set up a fallback email account to allow for the sending of :guilabel:`notifications`. The fallback email must be configured as a :guilabel:`general transactional server`. The :guilabel:`mail.default.from` system parameter must be set to the :guilabel:`username` of the general transactional server account. For more information see :ref:`Use a default email address `." +#: ../../content/administration/maintain/azure_oauth.rst:196 +msgid "Configuring a single outgoing server is the simplest configuration available for Microsoft Azure and it doesn't require extensive access rights for the users in the database." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:205 -#: ../../content/administration/maintain/mailjet_api.rst:213 -msgid "The :guilabel:`System Parameters` can be accessed by activating :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." +#: ../../content/administration/maintain/azure_oauth.rst:199 +msgid "A generic email address would be used to send emails for all users within the database. For example it could be structured with a `notifications` alias (`notifications@example.com`) or `contact` alias (`contact@example.com`). This address must be set as the :guilabel:`FROM Filtering` on the server. This address must also match the `{mail.default.from}@{mail.catchall.domain}` key combination in the system parameters." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:210 -msgid "Configure incoming email server" +#: ../../content/administration/maintain/azure_oauth.rst:206 +#: ../../content/administration/maintain/azure_oauth.rst:247 +msgid "For more information on the from filter visit: :ref:`email_communication/default`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:209 +#: ../../content/administration/maintain/azure_oauth.rst:254 +msgid "The :guilabel:`System Parameters` can be accessed by activating :ref:`developer-mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:212 +msgid "When using this configuration, every email that is sent from the database will use the address of the configured `notification` mailbox. However it should be noted that the name of the sender will appear but their email address will change:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:-1 +msgid "Name from real sender with static email." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:221 +msgid "Single outgoing mail server configuration:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:223 +msgid "Outgoing mail server **username** (login) = `notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:224 +msgid "Outgoing mail server :guilabel:`FROM Filtering` = `notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:225 +#: ../../content/administration/maintain/azure_oauth.rst:279 +msgid "`mail.catchall.domain` in system parameters = `example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:226 +#: ../../content/administration/maintain/azure_oauth.rst:280 +msgid "`mail.default.from` in system parameters = `notifications`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:229 +msgid "User-specific (multiple user) configuration" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:231 +msgid "In addition to a generic email server, individual email servers can be set up for users in a database. These email addresses must be set as the :guilabel:`FROM Filtering` on each individual server for this configuration to work." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:235 +msgid "This configuration is the more difficult of the two Microsoft Azure configurations, in that it requires all users configured with email servers to have access rights to settings in order to establish a connection to the email server." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:240 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:242 +msgid "Each user should have a separate email server set up. The :guilabel:`FROM Filtering` should be set so that only the user's email is sent from that server. In other words, only a user with an email address that matches the set :guilabel:`FROM Filtering` is able to use this server." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:249 +msgid "A :ref:`fallback server ` must be setup to allow for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering` for this server should have the value of the `{mail.default.from}@{mail.catchall.domain}`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:258 +msgid "The configuration for this transactional email server can work alongside an outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the mass-mailing email server can remain empty, but it's require to be added in the settings of the *Email Marketing* application." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:263 +msgid "For more information on setting the mass-mailing email server visit :ref:`email_communication/mass_mails`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:267 +msgid "Multiple user outgoing mail server configuration:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:270 +msgid "User #1 mailbox" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:270 +msgid "Outgoing mail server #1 **username** (login) = `john@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:271 +msgid "Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:273 +msgid "User #2 mailbox" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:273 +msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:274 +msgid "Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:276 +msgid "Notifications mailbox" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:276 +msgid "Outgoing mail server #3 **username** (login) = `notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:277 +msgid "Outgoing mail server #3 :guilabel:`FROM Filtering` = `notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:279 +msgid "System Parameters" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:283 +msgid "Configure incoming email server" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:285 msgid "The incoming account should be configured in a similar way to the outgoing email account. Navigate to the :guilabel:`Incoming Mail Servers` in the :guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check or Select the button next to :guilabel:`Outlook Oauth Authentication` and enter the :guilabel:`Microsoft Outlook username`. Click on :guilabel:`Connect your Outlook account`. Odoo will state: :guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the account. The account should be ready to receive email to the Odoo database." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:220 +#: ../../content/administration/maintain/azure_oauth.rst:293 msgid ":doc:`../../applications/general/email_communication/email_servers`" msgstr "" @@ -2792,6 +2888,10 @@ msgstr "" msgid "For more information see :ref:`Using a default email address `." msgstr "" +#: ../../content/administration/maintain/mailjet_api.rst:213 +msgid "The :guilabel:`System Parameters` can be accessed by activating :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." +msgstr "" + #: ../../content/administration/maintain/mailjet_api.rst:217 msgid "Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass mailing or transactional emails!" msgstr "" @@ -4494,10 +4594,6 @@ msgstr "" 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 "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 19b70a357..b695957b9 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-11 16:10+0000\n" +"POT-Creation-Date: 2023-10-09 08:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -120,7 +120,7 @@ msgid "The following financial :doc:`reports ` are availab msgstr "" #: ../../content/applications/finance/accounting.rst:127 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:232 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:365 msgid "Financial reports" msgstr "" @@ -179,7 +179,7 @@ msgstr "" #: ../../content/applications/finance/accounting.rst:149 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:135 #: ../../content/applications/finance/fiscal_localizations/chile.rst:161 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:90 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:124 #: ../../content/applications/finance/fiscal_localizations/peru.rst:321 msgid "Partner" msgstr "" @@ -429,12 +429,15 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:29 #: ../../content/applications/finance/fiscal_localizations/chile.rst:290 #: ../../content/applications/finance/fiscal_localizations/chile.rst:332 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:23 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:20 #: ../../content/applications/finance/fiscal_localizations/germany.rst:58 #: ../../content/applications/finance/fiscal_localizations/italy.rst:8 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:8 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:6 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:78 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:36 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:620 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:726 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:847 #: ../../content/applications/finance/fiscal_localizations/peru.rst:25 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:6 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:6 @@ -1713,6 +1716,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:5 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:86 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:310 msgid "Customer invoices" msgstr "" @@ -1737,7 +1741,7 @@ msgid "Invoicing in most countries occurs when a contractual obligation is met. msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:35 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:153 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:234 msgid "Invoice creation" msgstr "" @@ -1910,7 +1914,8 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:164 #: ../../content/applications/finance/fiscal_localizations/chile.rst:198 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:125 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:165 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:190 #: ../../content/applications/finance/fiscal_localizations/peru.rst:69 #: ../../content/applications/finance/fiscal_localizations/peru.rst:242 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:127 @@ -2742,7 +2747,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:97 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:26 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:32 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 #: ../../content/applications/finance/fiscal_localizations/france.rst:182 #: ../../content/applications/finance/fiscal_localizations/india.rst:16 @@ -2750,6 +2755,9 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:34 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:14 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:66 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:98 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:122 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:15 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:16 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:14 @@ -2758,13 +2766,16 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:98 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:27 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:36 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 #: ../../content/applications/finance/fiscal_localizations/india.rst:17 #: ../../content/applications/finance/fiscal_localizations/italy.rst:18 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:17 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:35 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:15 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:67 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:99 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:123 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:16 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:17 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:15 @@ -4011,6 +4022,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:79 #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 #: ../../content/applications/finance/fiscal_localizations/chile.rst:145 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:215 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:41 msgid "Chart of accounts" @@ -4873,7 +4885,6 @@ msgid "VAT unit tax report" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:5 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:498 msgid "Payments" msgstr "" @@ -5771,6 +5782,7 @@ msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" msgstr "" #: ../../content/applications/finance/accounting/payments/multiple.rst:10 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:403 msgid ":doc:`/applications/finance/accounting/bank/reconciliation`" msgstr "" @@ -7649,7 +7661,6 @@ msgid "Once the set fiscal period is over, Odoo automatically reverts to the def msgstr "" #: ../../content/applications/finance/accounting/reporting/year_end.rst:31 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1230 msgid "Year-end checklist" msgstr "" @@ -8170,7 +8181,7 @@ msgid ":doc:`taxes/B2B_B2C`" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:299 -msgid ":doc:`taxes/taxcloud`" +msgid ":doc:`taxes/taxcloud` (decommissioning TaxCloud integration in Odoo 17+)" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:300 @@ -8235,7 +8246,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:63 #: ../../content/applications/finance/fiscal_localizations/chile.rst:14 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:13 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:25 #: ../../content/applications/finance/fiscal_localizations/peru.rst:6 msgid "Introduction" msgstr "" @@ -8442,7 +8453,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:74 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:39 -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:151 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:159 msgid ":doc:`fiscal_positions`" msgstr "" @@ -8753,7 +8764,7 @@ msgid "To manually select which Fiscal Position to use for a new Sales Order, In msgstr "" #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:110 -msgid ":doc:`taxcloud`" +msgid ":doc:`taxcloud` (decommissioning TaxCloud integration in Odoo 17+)" msgstr "" #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:111 @@ -8816,15 +8827,23 @@ msgstr "" msgid "TaxCloud integration" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:5 -msgid "TaxCloud calculates the sales tax rate in real time for every state, city, and special jurisdiction in the United States. It keeps track of which products are exempt from sales tax and in which states each exemption applies." +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:6 +msgid "The Odoo TaxCloud integration has begun its decommissioning, starting in Odoo 17. New installations are prohibited in Odoo 17. In Odoo 18, the TaxCloud module(s) will **not** exist at all. Odoo recommends the use of the Avatax platform, instead." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:10 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:11 +msgid ":doc:`avatax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:13 +msgid "TaxCloud calculates the sales tax rate in real time for every state, city, and special jurisdiction in the United States. It keeps track of which products are exempt from sales tax, and in which states each exemption applies." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:18 msgid "TaxCloud registration" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:12 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:20 msgid "Register an account on `TaxCloud.com `_ and complete the setup. Once you go live, get the :guilabel:`TaxCloud API Keys` by clicking on :guilabel:`Stores`, then :guilabel:`Get Details`." msgstr "" @@ -8832,23 +8851,23 @@ msgstr "" msgid "Example of a store's TaxCloud API Keys" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:21 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:29 msgid "Enable TaxCloud" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:23 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:31 msgid "Go to :menuselection:`Accounting Dashboard --> Configuration --> Settings` and in the :guilabel:`Taxes` section enable :guilabel:`TaxCloud`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:25 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:33 msgid "Add the store's :guilabel:`Login ID` under :guilabel:`API ID` and the store's :guilabel:`Key` under :guilabel:`API KEY`. Click on :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:27 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:35 msgid "Click the :guilabel:`Refresh` button (:guilabel:`🗘`) next to :guilabel:`Default Category` to import the TIC :dfn:`Taxability Information Codes` product categories from TaxCloud. Some categories may imply specific tax rates or exemptions." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:30 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:38 msgid "Select a :guilabel:`Default Category` and :guilabel:`Save`. The :guilabel:`Default Category` is applied when no :guilabel:`TaxCloud Category` is set on your products or product categories, or when no product is found on an order/invoice." msgstr "" @@ -8856,43 +8875,43 @@ msgstr "" msgid "Filling in TaxCloud API Keys in Odoo" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:39 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:47 msgid "Set TaxCloud categories on products" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:41 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:49 msgid "If you need to use more than one TIC category (i.e., the :guilabel:`Default Category`), go to the product's :guilabel:`General Information` tab and select a :guilabel:`TaxCloud Category`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:44 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:52 msgid "If you want to configure multiple products simultaneously, ensure they share the same :guilabel:`Product Category` and click on the external link button (:guilabel:`🡕`) to set a :guilabel:`TaxCloud Category` on the :guilabel:`Product Category` instead." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:49 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:57 msgid "If you set a :guilabel:`TaxCloud Category` on a product and another on its :guilabel:`Product Category`, Odoo only considers the :guilabel:`TaxCloud Category` found on the product itself." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:52 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:60 msgid "A :guilabel:`TaxCloud Category` set on a **parent product category** does not apply to its **child product categories**. For example, if you set :guilabel:`TaxCloud Category` on the *All* :guilabel:`Product Category`, it is not applied to the *All/Sales* :guilabel:`Product Category`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:57 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:65 msgid "Make sure your company address is complete, including the state and the ZIP code. Go to :menuselection:`Settings --> Companies: Update Info` to open and edit your company address." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:61 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:69 msgid "Automatically post taxes in the correct tax payable account" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:63 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:71 msgid "To make sure the new taxes generated by the TaxCloud integration are created with the correct **Tax Payable** account, create a **user-defined default**. This process should be repeated for each one of your companies that uses TaxCloud." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:68 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:76 msgid "A user-defined default impacts all records at creation. It means that **every** new tax is set up to record income in the specified Tax Payable account unless the tax is manually edited to specify a different income account (or if another user-defined default takes precedence)." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:72 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:80 msgid "To do so, go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Chart of Accounts`, find the company's :guilabel:`Tax Payable` account, and click on :guilabel:`Setup`. Take note of the number after `id=` in the URL string; it is the **Tax Payable account ID** and will be used later." msgstr "" @@ -8900,11 +8919,11 @@ msgstr "" msgid "Example of Tax Payable account id in the URL string" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:81 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:89 msgid "Activate the :ref:`developer mode `, then go to :menuselection:`Settings --> Technical --> Actions: User-defined Defaults` and click on :guilabel:`Create`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:84 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:92 msgid "Click on :guilabel:`Field` drop-down menu and then on :guilabel:`Search More...`." msgstr "" @@ -8912,7 +8931,7 @@ msgstr "" msgid "User-defined Defaults Field search" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:90 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:98 msgid "Use the search bar to filter for the :guilabel:`Tax Repartition Line` model, and use it a second time to filter for the :guilabel:`Account` field. Select the line with :guilabel:`Tax Repartition Line` under the :guilabel:`Model` column." msgstr "" @@ -8920,11 +8939,11 @@ msgstr "" msgid "Searching for the Tax Repartition Line model and Account field" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:98 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:106 msgid "Once you are back to the :guilabel:`User-defined Defaults` creation, enter the **Tax Payable account ID** you took note of earlier under the :guilabel:`Default Value (JSON format)` field." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:101 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:109 msgid "Select the company for which this configuration should apply under the :guilabel:`Company` field and click :guilabel:`Save`." msgstr "" @@ -8932,15 +8951,15 @@ msgstr "" msgid "Example of a User-defined Defaults configuration" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:109 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:117 msgid "Automatically detect the fiscal position" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:111 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:119 msgid "Sales taxes are calculated in Odoo based on :doc:`fiscal positions `. A fiscal position for the United States is created when enabling TaxCloud." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:114 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:122 msgid "You can configure Odoo to automatically detect to which customers the fiscal position should be applied. To do so, go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Fiscal Positions` and select :guilabel:`Automatic Tax Mapping (TaxCloud)`. Enable :guilabel:`Detect Automatically` and then :guilabel:`Save`." msgstr "" @@ -8948,27 +8967,27 @@ msgstr "" msgid "Detect Automatically setting on the TaxCloud fiscal position" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:123 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:131 msgid "Now, this fiscal position is automatically set on any order or invoice if the customer country is *United States*. This triggers the automated tax computation." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:127 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:135 msgid "To get the sales taxes on a sales order, confirm it or click the :guilabel:`Update Taxes` button next to :guilabel:`Add Shipping`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:131 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:139 msgid "Interaction with coupons and promotions" msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:133 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:141 msgid "If you use the **Coupon** or **Promotion Programs**, the integration with TaxCloud might behave unexpectedly. Indeed, as TaxCloud does not accept lines with negative amounts as part of the tax computation, the amount of the lines added by the promotion program must be deduced from the total of the lines it impacts." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:139 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:147 msgid "This means, amongst other complications, that orders using coupons or promotions with a TaxCloud fiscal position **must** be invoiced completely - you cannot create invoices for partial deliveries, etc." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:143 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:151 msgid "Another unexpected behavior is possible. For example, you sell a product for which you have a promotion program that provides a 50% discount. If the product's tax rate is 7%, the tax rate computed from the TaxCloud integration displays 3.5%. This happens because the discount is included in the price sent to TaxCloud. However, in Odoo, the discount is on another line entirely. Still, the tax computation is correct. Indeed, a 3.5% tax on the full price is the equivalent of a 7% tax on half the price, but this might be unexpected from a user point of view." msgstr "" @@ -10815,13 +10834,13 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:6 #: ../../content/applications/finance/fiscal_localizations/chile.rst:6 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:6 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:18 msgid "Webinars" msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:8 #: ../../content/applications/finance/fiscal_localizations/chile.rst:8 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:8 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:20 msgid "Below you can find videos with a general description of the localization, and how to configure it." msgstr "" @@ -10834,8 +10853,9 @@ msgid "`VIDEO WEBINAR ECOMMERCE `_. msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:17 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:26 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:23 #: ../../content/applications/finance/fiscal_localizations/germany.rst:61 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:57 msgid "Modules installation" msgstr "" @@ -10844,7 +10864,7 @@ msgid ":ref:`Install ` the following modules to get all the fea msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:28 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:37 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 #: ../../content/applications/finance/fiscal_localizations/france.rst:59 #: ../../content/applications/finance/fiscal_localizations/india.rst:18 @@ -10852,6 +10872,9 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:68 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:100 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:124 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 @@ -10907,6 +10930,7 @@ msgid "(optional) Allows the user to see Identification Type and AFIP Responsibi msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:47 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:144 #: ../../content/applications/finance/fiscal_localizations/peru.rst:43 msgid "Configure your company" msgstr "" @@ -11935,7 +11959,11 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:39 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:40 -msgid "Review in progress" +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:47 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:51 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:52 +msgid "Certified" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:41 @@ -11955,13 +11983,6 @@ msgstr "" msgid "Odoo 15.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:47 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:51 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:52 -msgid "Certified" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/belgium.rst:50 msgid "Odoo 14.0" msgstr "" @@ -12266,6 +12287,7 @@ msgid "Fiscal reports parameters." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:134 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:533 #: ../../content/applications/finance/fiscal_localizations/peru.rst:226 msgid "Multicurrency" msgstr "" @@ -13181,356 +13203,513 @@ msgstr "" msgid "Colombia" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:5 -msgid "The following documentation covers the Colombian localization modules and their basic concepts to understand, implement, and use Colombian localization in Odoo." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:8 -msgid "Configure Master Data for Colombia" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:9 -msgid "Use and configure Electronic Invoicing in Odoo for Colombia." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:7 +msgid "Odoo's Colombian localization package provides accounting, fiscal and legal features in Colombia such as chart of accounts, taxes and electronic invoicing." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:10 -msgid ":ref:`Invoice creation ` and :ref:`validation `" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:12 -msgid ":ref:`Reception of legal XML and PDF `" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:13 -msgid ":ref:`Avoid common mistakes `" +msgid "In addition, we have a series of videos covering how to start from scratch, configuration, main workflows, and specific use cases." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:14 -msgid ":ref:`Financial reports `" +msgid "`Odoo Colombian localization videos `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:17 -msgid "`Smart Tutorial - Localización de Colombia `_" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:28 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:25 msgid ":ref:`Install ` the following modules to get all the features of the Colombian localization:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:38 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 msgid ":guilabel:`Colombia - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:39 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:36 msgid "`l10n_co`" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:37 +msgid "Default :ref:`fiscal localization package `. This module adds the base accounting features for the Colombian localization: chart of accounts, taxes, withholdings, identification document type." +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/colombia.rst:40 -#: ../../content/applications/finance/fiscal_localizations/egypt.rst:21 -#: ../../content/applications/finance/fiscal_localizations/india.rst:21 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:22 -#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:19 -#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:20 -msgid "Default :ref:`fiscal localization package `" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:41 -msgid ":guilabel:`Electronic invoicing for Colombia with Carvajal`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:42 -msgid "`l10n_co_edi`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:43 -msgid "Carvajal e-invoicing integration" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:44 -msgid ":guilabel:`Colombian - Point of Sale`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:45 -msgid "`l10n_co_pos`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:46 -msgid "Point of Sale" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:47 msgid ":guilabel:`Colombian - Accounting Reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:48 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:41 msgid "`l10n_co_reports`" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:42 +msgid "Includes accounting reports for sending certifications to suppliers for withholdings applied." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:43 +msgid ":guilabel:`Electronic invoicing for Colombia with Carvajal`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:44 +msgid "`l10n_co_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:45 +msgid "This module includes the features that are required for the integration with Carvajal and generates the electronic invoices and support document related to the vendor bills based on |DIAN| regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:48 +msgid ":guilabel:`Colombian - Point of Sale`" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/colombia.rst:49 -msgid "Colombian reports" +msgid "`l10n_co_pos`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:52 -msgid "Configure credentials for Carvajal web service" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:50 +msgid "Includes Point of Sale Receipt for Colombian Localization." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:54 -msgid "Once the modules are installed, the user credentials need to be configured in order to connect with Carvajal Web Service. First, navigate to :menuselection:`Accounting --> Configuration --> Settings` and look for the :guilabel:`Colombian Electronic Invoice` section. Then, fill in the required configuration information provided by Carvajal." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:53 +msgid "When a database is created from scratch selecting :guilabel:`Colombia` as the country, Odoo automatically installs the base modules *Colombia - Accounting* and *Colombia - Accounting Reports*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:58 +msgid "Company configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:60 +msgid "To configure your company information, go to the :menuselection:`Contacts` app and search for your company. Alternatively, activate :ref:`developer mode ` and navigate to :menuselection:`General Setting --> Company --> Update Info --> Contact`. Then, edit the contact form to configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:65 +msgid ":guilabel:`Company Name`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:66 +msgid ":guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department` and :guilabel:`Zip Code`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:67 +msgid ":guilabel:`Tax ID`: When it is a `NIT`, it must have the *verification digit* at the end of the ID followed by a hyphen (`-`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:70 +msgid "Next, configure the :guilabel:`Fiscal Information` in the :guilabel:`Sales & Purchase` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:72 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:147 +msgid ":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company (:guilabel:`O-13` Gran Contribuyente, :guilabel:`O-15` Autorretenedor, :guilabel:`O-23` Agente de retención IVA, :guilabel:`O-47` Regimen de tributación simple, :guilabel:`R-99-PN` No Aplica)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:75 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:150 +msgid ":guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this option should be selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:77 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:152 +msgid ":guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (:guilabel:`IVA`, :guilabel:`INC`, :guilabel:`IVA e INC`, :guilabel:`No Aplica`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:79 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:154 +msgid ":guilabel:`Commercial Name`: If the company uses a specific commercial name, and it needs to be displayed in the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:83 +msgid "Carjaval credentials configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:85 +msgid "Once the modules installed, the user credentials must be configured in order to connect with Carvajal Web Service. Navigate to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the required configuration information provided by Carvajal:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:90 +msgid ":guilabel:`Username` and :guilabel:`Password`: Correspond to the username and password provided by Carvajal to the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:92 +msgid ":guilabel:`Company Registry`: Company's NIT number *without* the verification code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:93 +msgid ":guilabel:`Account ID`: Company ID followed by `_01`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:94 +msgid ":guilabel:`Colombia Template Code`: Select one of the two available templates (:guilabel:`CGEN03` or :guilabel:`CGNE04`) to be used in the PDF format of the electronic invoice." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "Configure credentials for Carvajal web service in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:62 -msgid "Check the :guilabel:`Test mode` checkbox to connect with the Carvajal testing environment. This allows users to test the complete workflow and integration with the :abbr:`CEN (Centro Electrónico de Negocios)` Financiero portal, which is accessible here:" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:101 +msgid "Check the :guilabel:`Test mode` checkbox to connect with the Carvajal testing environment. Once Odoo and Carvajal are fully configured and ready for production, uncheck the :guilabel:`Test mode` checkbox to use the production database." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:66 -msgid "`CTS (Carvajal T&S) `_." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:67 -msgid "`CSC (Carvajal Servicios de Comunicación) `_." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:69 -msgid ":abbr:`CSC (Carvajal Servicios de Comunicación)` is the default for new databases." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:71 -msgid "Once Odoo and Carvajal are fully configured and ready for production, the testing environment can be disabled by unchecking the :guilabel:`Test mode` checkbox." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:75 -msgid "Configure report data" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:77 -msgid "Report data can be defined for the fiscal section and the bank information in the PDF as part of the configurable information that is sent in the XML." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:80 -msgid "Navigate to :menuselection:`Accounting --> Configuration --> Settings` and look for the :guilabel:`Colombian Electronic Invoice` section." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 -msgid "Configure the report data in Odoo." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:87 -msgid "Configure data required in the XML" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:92 -msgid "Configure the identification number and fiscal structure." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:95 -msgid "Identification" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:97 -msgid "As part of the Colombian Localization, the document types defined by the :abbr:`DIAN (Dirección de Impuestos y Aduanas Nacionales)` are now available on the Partner form. Colombian partners have to have their identification number (:guilabel:`VAT`) and :guilabel:`Document Type` set:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 -msgid "The document type of RUT set in Odoo." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:105 -msgid "When the :guilabel:`Document Type` is `RUT`, the identification number needs to be configured in Odoo, including the verification digit, Odoo will split this number when the data to the third-party vendor is sent." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:106 +msgid ":guilabel:`Test mode` must be used **only** on replicated databases, **not** the production environment." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:110 -msgid "Fiscal structure (RUT)" +msgid "Report data configuration" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:112 -msgid "The partner's responsibility codes (section 53 in the RUT document) are included as part of the electronic invoice module, given it is part of the information required by the :abbr:`DIAN (Dirección de Impuestos y Aduanas Nacionales)`." +msgid "Report data can be defined for the fiscal section and bank information of the PDF as part of the configurable information sent in the XML." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:116 -msgid "The required fields can be found in :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal Information`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:115 +msgid "Navigate to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 -msgid "The fiscal information included in the electronic invoice module in Odoo." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:122 -msgid "Additionally, two boolean fields were added in order to specify the fiscal regimen of the partner." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:121 +msgid "Master data configuration" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:127 -msgid "If sales transactions include products with taxes, the :guilabel:`Value Type` field in the :guilabel:`Advanced Options tab` needs to be configured per tax." +msgid "Identification information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:130 -msgid "Retention tax types (ICA, IVA, Fuente) are also included in the options to configure taxes. This configuration is used in order to display taxes in the invoice PDF correctly." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:129 +msgid "Document types defined by the |DIAN| are available on the partner form as part of the Colombian localization. Colombian partners must have their :guilabel:`Identification Number` (VAT) and :guilabel:`Document Type` set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:134 +msgid "When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification Number` needs to be configured in Odoo, including the *verification digit*; Odoo splits this number when the data to is sent to the third party." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:139 +msgid "Fiscal information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:141 +msgid "The partner's responsibility codes (section 53 in the RUT document) are included as part of the electronic invoicing module, as it is required by the |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:144 +msgid "The required fields can be found under :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal Information`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:158 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:246 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:662 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:771 +msgid "Products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:160 +msgid "In addition to adding general information (in the :guilabel:`General Information` tab) on the product form, either the :guilabel:`UNSPSC Category`, :guilabel:`Barcode`, or :guilabel:`Internal Reference` field must also be configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:167 +msgid "If sales transactions include products with taxes, the :guilabel:`Value Type` field in the :guilabel:`Advanced Options` tab needs to be configured per tax. To do so, go to :menuselection:`Accounting --> Configuration --> Taxes`, and select the related tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:171 +msgid "Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`, :guilabel:`Fuente`) are also included. This configuration is used to display taxes in the invoice PDF correctly." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "The ICA, IVA and Fuente fields in the Advanced Options tab in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:137 -msgid "Users" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:178 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:91 +msgid "Sales journals" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:139 -msgid "The default template that is used by Odoo on the invoice PDF includes the job position of the salesperson, so the :guilabel:`Job Position` field should be configured." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:182 +msgid "Once the |DIAN| has assigned the official sequence and prefix for the electronic invoice resolution, the sales journals related to the invoice documents must be updated in Odoo. To do so, navigate to :menuselection:`Accounting --> Configuration --> Journals`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:145 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:186 +msgid "Configure the following data in the :guilabel:`Advanced Settings` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:188 +msgid ":guilabel:`Electronic invoicing`: Enable :guilabel:`UBL 2.1 (Colombia)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:189 +msgid ":guilabel:`Invoicing Resolution`: Resolution number issued by |DIAN| to the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:190 +msgid ":guilabel:`Resolution Date`: Initial effective date of the resolution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:191 +msgid ":guilabel:`Resolution end date`: End date of the resolution's validity." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 +msgid ":guilabel:`Range of Numbering (minimum)`: First authorized invoice number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:193 +msgid ":guilabel:`Range of Numbering (maximum)`: Last authorized invoice number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:196 +msgid "The sequence and resolution of the journal must match the one configured in Carvajal and the |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:200 +msgid "Invoice sequence" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:202 +msgid "The invoice sequence and prefix must be correctly configured when the first document is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:205 +msgid "Odoo automatically assigns a prefix and sequence to the following documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:208 +msgid "Purchase journals" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:210 +msgid "Once the |DIAN| has assigned the official sequence and prefix for the support document related to vendor bills, the purchase journals related to their supporting documents need to be updated in Odoo. The process is similar to the configuration of the :ref:`sales journals `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:217 +msgid "The :doc:`chart of accounts ` is installed by default as part of the localization module, the accounts are mapped automatically in taxes, default account payable, and default account receivable. The chart of accounts for Colombia is based on the PUC (Plan Unico de Cuentas)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:226 msgid "Main workflows" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 -msgid "Electronic invoice workflow in Odoo." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:229 +msgid "Electronic invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:155 -msgid "The functional workflow that takes place before an invoice validation doesn't change. The main changes that are introduced with the electronic invoice are the next fields." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:237 +msgid "The functional workflow taking place before an invoice validation does not alter the main changes introduced with the electronic invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:158 -msgid "There are three types of documents:" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:240 +msgid "Electronic invoices are generated and sent to both the |DIAN| and customer through Carvajal's web service integration. These documents can be created from your sales order or manually. Go to :menuselection:`Accounting --> Customers --> Invoices` and configure:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:160 -msgid "**Factura Electronica**: This is the regular document type applicable for Invoices, Credit Notes and Debit Notes." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:244 +msgid ":guilabel:`Customer`: Customer's information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:162 -msgid "**Factura de Importación**: This should be selected for importation transactions." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:245 +msgid ":guilabel:`Journal`: Journal used for electronic invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:163 -msgid "**Factura de contingencia**: This is an exceptional type that is used as a manual backup if the company is not able to use the ERP and if it is necessary to generate the invoice manually when this invoice is added to the ERP." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:246 +msgid ":guilabel:`Electronic Invoice Type`: Select the type of document. By default, :guilabel:`Factura de Venta` is selected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:170 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:248 +msgid ":guilabel:`Invoice Lines`: Specify the products with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:250 +msgid "When done, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:255 #: ../../content/applications/finance/fiscal_localizations/india.rst:117 #: ../../content/applications/finance/fiscal_localizations/india.rst:262 #: ../../content/applications/finance/fiscal_localizations/peru.rst:385 msgid "Invoice validation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:172 -msgid "After the invoice is validated, an XML file is created and sent automatically to Carvajal. This file is also displayed in the chatter." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:257 +msgid "After the invoice confirmation, an XML file is created and sent automatically to Carvajal. The invoice is then processed asynchronously by the E-invoicing service UBL 2.1 (Colombia). The file is also displayed in the chatter." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "Carvajal XML invoice file in Odoo chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:178 -msgid "The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`Other Info` tab with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is displayed with the initial value :guilabel:`In progress`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:264 +msgid "The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`EDI Documents` tab with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is displayed with the initial value :guilabel:`To Send`. To process the invoice manually, click on the :guilabel:`Process Now` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:185 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:272 msgid "Reception of legal XML and PDF" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:187 -msgid "The electronic invoice vendor receives the XML file and proceeds to validate the structure and the information in it. In the :guilabel:`Action` drop-down menu, select the :guilabel:`Check Carvajal Status` button. If everything is correct, the :guilabel:`Electronic Invoice Status` field value changes to :guilabel:`Validated`. Then, proceed to generate a legal XML, which includes a digital signature and a unique code (CUFE), a PDF invoice that includes a QR code, and the CUFE is also generated." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:274 +msgid "The electronic invoice vendor (Carvajal) receives the XML file and proceeds to validate its structure and information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:194 -msgid "After this:" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:277 +msgid "After validating the electronic invoice, proceed to generate a legal XML which includes a digital signature and a unique code (CUFE), a PDF invoice that includes a QR code and the CUFE is also generated. If everything is correct the :guilabel:`Electronic Invoicing` field value changes to :guilabel:`Sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:196 -msgid "A ZIP containing the legal XML and the PDF is downloaded and displayed in the invoice chatter:" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:282 +msgid "A ZIP containing the legal electronic invoice in XML format and the invoice in PDF format is downloaded and displayed in the invoice chatter:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:0 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "ZIP file displayed in the invoice chatter in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:0 -msgid "XML and PDF contained in invoice ZIP file." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:204 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:288 msgid "The electronic invoice status changes to :guilabel:`Accepted`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:209 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:291 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:335 +msgid "Credit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:293 +msgid "The process for credit notes is the same as for invoices. To create a credit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click :guilabel:`Add Credit Note` and complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:297 +msgid ":guilabel:`Credit Method`: Select the type of credit method." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:299 +msgid ":guilabel:`Partial Refund`: Use this option when it is a partial amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:300 +msgid ":guilabel:`Full Refund`: Use this option if the credit note is for the full amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:301 +msgid ":guilabel:`Full refund and new draft invoice`: Use this option if the credit note is auto-validated and reconciled with the invoice. The original invoice is duplicated as a new draft." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:305 +msgid ":guilabel:`Reason`: Enter the reason for the credit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:306 +msgid ":guilabel:`Reversal Date`: Select if you want a specific date for the credit note or if it is the journal entry date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:308 +msgid ":guilabel:`Use Specific Journal`: Select the journal for your credit note or leave it empty if you want to use the same journal as the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:310 +msgid ":guilabel:`Refund Date`: If you chose a specific date, select the date for the refund." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:312 +msgid "Once reviewed, click the :guilabel:`Reverse` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:315 +msgid "Debit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:317 +msgid "The process for debit notes is similar to credit notes. To create a debit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click the :guilabel:`Add Debit Note` button and complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:321 +msgid ":guilabel:`Reason`: Type the reason for the debit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:322 +msgid ":guilabel:`Debit note date`: Select the specific options." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:323 +msgid ":guilabel:`Copy lines`: Select this option if you need to register a debit note with the same lines of invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:325 +msgid ":guilabel:`Use Specific Journal`: Select the printer point for your debit note, or leave it empty if you want to use the same journal as the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:328 +msgid "When done, click :guilabel:`Create Debit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:331 +msgid "Support document for vendor bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:333 +msgid "With master data, credentials, and the purchase journal configured for support documents related to vendor bills, you can start using support documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:336 +msgid "Support documents for vendor bills can be created from your purchase order or manually. Go to :menuselection:`Accounting --> Vendors --> Bills` and fill in the following data:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:339 +msgid ":guilabel:`Vendor`: Enter the vendor's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:340 +msgid ":guilabel:`Bill Date`: Select the date of the bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:341 +msgid ":guilabel:`Journal`: Select the journal for support documents related to the vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:342 +msgid ":guilabel:`Invoiced Lines`: Specify the products with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 +msgid "Once reviewed, click the :guilabel:`Confirm` button. Upon confirmation, an XML file is created and automatically sent to Carvajal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:350 msgid "Common errors" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:211 -msgid "During the XML validation, the most common errors are usually related to missing master data. In such cases, error messages are shown in the chatter after updating the electronic invoice status." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:352 +msgid "During the XML validation, the most common errors are related to missing master data (*Contact Tax ID*, *Address*, *Products*, *Taxes*). In such cases, error messages are shown in the chatter after updating the electronic invoice status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:356 +msgid "After the master data is corrected, it's possible to reprocess the XML with the new data and send the updated version, using the :guilabel:`Retry` button." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "XML validation errors shown in the invoice chatter in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:217 -msgid "After the master data is corrected, it's possible to reprocess the XML with the new data and send the updated version, using the following button in the :guilabel:`Action` drop-down menu." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 -msgid "The updated invoice status in Odoo." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:224 -msgid "Additional use cases" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:226 -msgid "The process for credit and debit notes is exactly the same as the invoice. The functional workflow remains the same as well." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:234 -msgid "This information is a quick reference to the accounting reports included in the *Colombian Localization Accounting Reports* module." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:238 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 msgid "Certificado de Retención en ICA" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:240 -msgid "This report is a certification to vendors for withholdings made for the Colombian Industry and Commerce tax (ICA)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:243 -msgid "Go to :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en ICA`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:370 +msgid "This report is a certification to vendors for withholdings made for the Colombian Industry and Commerce (ICA) tax. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en ICA`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "Certificado de Retención en ICA report in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:250 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:378 msgid "Certificado de Retención en IVA" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:252 -msgid "This report issues a certificate on the amount withheld from vendors for VAT withholding." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:254 -msgid "Go to :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en IVA`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:380 +msgid "This report issues a certificate on the amount withheld from vendors for VAT withholding. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en IVA`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "Certificado de Retención en IVA report in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:261 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:388 msgid "Certificado de Retención en la Fuente" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:263 -msgid "This certificate is issued to partners for the withholding tax that they have made." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:265 -msgid "Go to :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en Fuente`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:390 +msgid "This certificate is issued to partners for the withholding tax that they have made. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en Fuente`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 @@ -13559,6 +13738,14 @@ msgstr "" msgid "``l10n_eg``" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:21 +#: ../../content/applications/finance/fiscal_localizations/india.rst:21 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:22 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:19 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:20 +msgid "Default :ref:`fiscal localization package `" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/egypt.rst:22 msgid ":guilabel:`Egyptian E-invoice Integration`" msgstr "" @@ -13787,11 +13974,6 @@ msgstr "" msgid "You can edit your customers' contact forms by going to :menuselection:`Accounting --> Customers --> Customers`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:378 -msgid "Products" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/egypt.rst:174 msgid "Make sure your products are correctly configured so your e-invoices are valid:" msgstr "" @@ -15966,7 +16148,6 @@ msgid "Italy's electronic document invoicing options" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:150 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Taxes configuration" msgstr "" @@ -16674,1843 +16855,1290 @@ msgstr "" msgid "Mexico" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:10 -msgid "`VIDEO WEBINAR OF A COMPLETE DEMO `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:22 +msgid "`Video webinar of a complete demo `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:15 -msgid "Odoo Enterprise users in Mexico have free access to a set of modules that allow them to issue electronic invoices according to the specifications of the SAT for `version 3.3 of the CFDI `_, a legal requirement as of January 1, 2018. These modules also add relevant accounting reports (for example, the DIOT), and enable foreign trade, with support for associated customs operations." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:21 -msgid "With the Mexican location in Odoo you will not only be able to comply with the legal requirements to invoice in Mexico, but also use it as your accounting system, satisfying the normal needs of the market. This makes Odoo the perfect solution to manage your business in Mexico." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:26 -msgid "Pre requirements" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:28 -msgid "Before installing the modules and making the necessary configurations to have the Mexican localization in Odoo, it is necessary to meet the following requirements:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:31 -msgid "Be registered with the SAT and have an RFC." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:27 +msgid "Odoo users in Mexico have access to a set of modules that allow them to sign electronic invoices according to the specifications of the |SAT| for `version 4.0 of the CFDI `_ , a legal requirement as of January 1, 2022." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:32 -msgid "Have a `Certificate of Digital Seal `_ (CSD)." +msgid "These modules also add relevant accounting reports (such as the |DIOT|, enable foreign trade, and the creation of delivery guides)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:34 -msgid "Choose a PAC and purchase stamps. Currently the Mexican location in Odoo works with the following PACs: `Solución Factible `_, `Quadrum (formerly Finkok) `_ and `SW Sapien - Smarter Web `_." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:37 -msgid "Have knowledge and experience with billing, sales and accounting in Odoo. This documentation contains only the information necessary to enable the use of Odoo in a company based in Mexico." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:39 +msgid "Requirements" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:41 -msgid "Modules" +msgid "Before making the necessary configurations to have the Mexican localization installed in Odoo, it is necessary to meet the following requirements:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:43 -msgid "To install the Mexican localization module, go to :menuselection:`Apps`, then remove the default filter \"Apps\" and search for ``l10n_mx``." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:46 +msgid "Be registered in the |SAT|, with a valid :abbr:`RFC (Registro Federal de Contribuyentes)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Installation of the Mexican localization module in Odoo Apps" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:47 +msgid "Have a `Certificate of Digital Seal `_ (CSD)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:51 -msgid "If you created the database from `www.odoo.com `_ and chose \"Mexico\" as the country when creating your account, some of the Mexican localization modules will have been installed automatically. In that case we observe that some modules have a button that says \"Install\", while others will instead have a label that says \"Installed\"." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:49 +msgid "Choose a PAC (Proveedor Autorizado de Certificación / Authorized Certification Provider). Currently, Odoo works with the following |PAC|\\s: `Solución Factible `_, `Quadrum (formerly Finkok) `_ and `SW Sapien - Smarter Web `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:56 -msgid "The following modules are necessary for all databases that require Mexican localization:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:53 +msgid "Have knowledge and experience with billing, sales, and accounting in Odoo. This documentation contains only the necessary information to use Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "**Mexico - Accounting (l10n_mx)**" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:59 +msgid ":ref:`Install ` the following modules to get the main features of the Mexican localization:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "All the basic data to manage accounting, taxes and the chart of accounts. The installed chart of accounts is based on `the SAT account grouping code `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:69 +msgid ":guilabel:`Mexico - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "**EDI for Mexico (l10n_mx_edi & l10n_mx_edi_extended)**" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:70 +msgid "`l10n_mx`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "Necessary for electronic transactions, CFDI 3.3, payment complement, and addenda on invoices." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 +msgid "The default :doc:`fiscal localization package `, adds accounting characteristics for the Mexican localization, such as the most common taxes and the chart of accounts based on `the SAT account grouping code `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "**Odoo Mexican localization reports (l10n_mx_reports & l10n_mx_reports_closing)**" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:75 +msgid ":guilabel:`EDI for Mexico`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "All mandatory reports for electronic accounting. (Requires the accounting application)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:76 +msgid "`l10n_mx_edi`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:67 -msgid "The following modules are optional, and should be installed only if they meet a specific organization requirement. Installing these modules is not recommended unless you are sure they are needed as they add fields that can unnecessarily complicate form filling." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:77 +msgid "Includes all the technical and functional requirements to generate and validate :doc:`Electronics Documents `, based on the technical documentation published by the SAT. This allows you to send invoices (with or without addendas) and payment complements to the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "**Odoo Mexico Localization for Stock / Landing (l10n_mx_edi_landing)**" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "This module allows managing the requests as part of the shipping costs." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "**Odoo Mexican XML Polizas Export (l10n_mx_xml_polizas)**" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "With this module, you will be able to export your Journal Entries in XML ready to be uploaded to the SAT." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:81 -msgid "Enable electronic invoicing" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:82 +msgid ":guilabel:`EDI v4.0 for Mexico`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:83 -msgid "Go to :menuselection:`Settings --> Accounting --> Customer Invoices`, and make sure that the option **Mexican Electronic Invoicing** is enabled. With this you will be able to generate the signed invoice and also generate the signed payment complement, all automatically integrated into the normal billing flow in Odoo." +msgid "`l10n_mx_edi_40`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Steps to enable electronic invoicing" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:84 +msgid "Necessary to create XML documents with the correct specifications of the CFDI 4.0." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:95 -msgid "Enter legal information" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:87 +msgid "When you install a database from scratch by selecting :guilabel:`Mexico` as the country, Odoo automatically installs the following modules: :guilabel:`Mexico - Accounting`, :guilabel:`EDI for Mexico`, and :guilabel:`EDI v4.0 for Mexico`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:97 -msgid "After verifying the general configuration, you must verify that the company is configured with the correct data. To do so, go to :menuselection:`Settings --> General Settings --> Companies`, and click on *Update information* under your company name." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:91 +msgid "The following modules are needed to add Mexico's Electronic Accounting. They require the :doc:`Accounting ` module to be installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Update the company's details in the Settings of Odoo" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:101 +msgid ":guilabel:`Odoo Mexican Localization Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:102 +msgid "`l10n_mx_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:103 +msgid "Adapts reports for Mexico's Electronic Accounting: Chart of Accounts, Trial Balance, and DIOT." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:105 -msgid "In the resulting form, put your full address (including zip code), RFC (VAT number), and the rest of the data." +msgid ":guilabel:`Mexico - Localization Reports for Closing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:106 +msgid "`l10n_mx_reports_closing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:107 +msgid "Necessary to create the Closing Entry (Also known as the month 13th move)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:108 +msgid ":guilabel:`Odoo Mexican XML Polizas Export`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:109 -msgid "From a legal point of view, a Mexican company must use the local currency (MXN). Therefore, Odoo does not provide features to manage an alternative configuration. If you want to manage another currency, let MXN be the default currency and use a :doc:`pricelist ` instead." +msgid "`l10n_mx_xml_polizas`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:110 +msgid "Lets you export XML files of your Journal Entries for a compulsory audit." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:111 +msgid ":guilabel:`Odoo Mexican XML Polizas Export Edi bridge`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:112 +msgid "`l10n_mx_xml_polizas_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:113 +msgid "Complements the module `l10n_mx_xml_polizas`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 -msgid "Make sure that in the address, for the Country field, \"Mexico\" is chosen from the list of countries that Odoo shows, because if it is entered manually there is a risk of creating a \"new country\" in the system, which it will result in errors later when the CFDIs are generated." +msgid "The following modules are optional. It's recommended to install them *only* if you meet a specific requirement. Make sure that they are needed for your business." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "Company data information" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:125 +msgid ":guilabel:`EDI for Mexico (Advanced Features)`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:124 -msgid "If you want to test the Mexican localization, you can configure the company with a real address within Mexico (including all fields) and add ``EKU9003173C9`` as RFC." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:126 +msgid "`l10n_mx_edi_extended`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:128 -msgid "Set the fiscal regime of the company" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:127 +msgid "Adds the external trade complement to invoices: A legal requirement for selling products to foreign countries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:129 +msgid ":guilabel:`EDI v4.0 for Mexico (COMEX)`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:130 -msgid "The following is to indicate what is the fiscal regime of the company that we are configuring, which is done through a pre-existing field in Odoo called \"Fiscal Regime\"." +msgid "`l10n_mx_edi_extended_40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:131 +msgid "Adapts the module `l10n_mx_edi_extended` for CFDI 4.0." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:132 +msgid ":guilabel:`Mexico - Electronic Delivery Guide`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:133 -msgid "Go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX) --> Fiscal Regime`, and select the option that applies to your company from the drop-down list." +msgid "`l10n_mx_edi_stock`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Set the Fiscal Regime in Odoo Accounting" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:134 +msgid "Lets you create a \"Carta Porte\": a bill of lading that proves to the government you are sending goods between A & B with a signed electronic document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:136 +msgid ":guilabel:`Electronic Delivery Guide for Mexico CFDI 4.0`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 +msgid "`l10n_mx_edi_stock_40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:138 +msgid "Adapts the module `l10n_mx_edi_stock` for CFDI 4.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:139 +msgid ":guilabel:`Odoo Mexico Localization for Stock/Landing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:140 +msgid "`l10n_mx_edi_landing`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:141 -msgid "For the test environment: Select the option **General Law on Legal Persons** from the drop-down menu." +msgid "Allows managing customs numbers related to landed costs in electronic documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:145 -msgid "Contacts Configuration" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:146 +msgid "After installing the correct modules, you must verify that the company is configured with the correct data. To do so, go to :menuselection:`Settings --> General Settings --> Companies` and select :guilabel:`Update Info` under your company name." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:147 -msgid "When creating a contact to be invoiced in Odoo, the following information must be configured for invoice validation: **complete address** (including postal code, city, state, country, etc.) and the **VAT** number." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:150 +msgid "Enter your full :guilabel:`Address` in the resulting form including :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and RFC (:guilabel:`VAT` number)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:153 +msgid "According to the requirements of the CFDI 4.0, the name of your main contact must coincide to your business name registered in the SAT without the legal entity abbreviation." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Contact form example" +msgid "Requirements for a correct invoicing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:156 -msgid "Taxes Configuration" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:160 +msgid "From a legal point of view, a Mexican company must use the local currency (MXN). Therefore, Odoo does not provide features to manage an alternative configuration. If you want to manage another currency, let MXN be the default currency and use a :doc:`pricelist ` instead." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:158 -msgid "A necessary configuration for electronic invoicing to work correctly in Odoo is to add the factor type associated with sales taxes." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:161 -msgid "To make this configuration you first have to go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:164 -msgid "Within the list of taxes that are pre-loaded, select the option *Sales* on the filter, this is to see only taxes associated with sales, which are those that are validated for the stamping of invoices. Open the form view of any of the sales taxes, select the **Advanced Options** tab and within the field **Factor Type** choose the option *Tasa*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:173 -msgid "Do the same for all the sales taxes that the company needs, either those that come by default in Odoo, or those that you add that are necessary for your company bill." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:177 -msgid "For the 0% VAT tax, select the option :guilabel:`Tasa` within the :guilabel:`Factor Type` field. For the 0% VAT **exempt** tax, select the option :guilabel:`Exento` instead of :guilabel:`Tasa` within the :guilabel:`Factor Type` field." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:181 -msgid "When registering a payment, Odoo will carry out the movement of taxes from the **Cash Basis Transition Account** to the account set in the **Definition** tab. For such movement, a tax base account will be used (\"Base Imponible de Impuestos en Base a Flujo de Efectivo\" - **do not eliminate this account**) in the Journal Entry when reclassifying taxes." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:165 +msgid "Next, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX) --> Fiscal Regime`, and select the regime that applies to your company from the drop-down list." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Taxes accounts" +msgid "Fiscal regime configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:191 -msgid "Products Configuration" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:172 +msgid "If you want to test the Mexican localization, you can configure the company with a real address within Mexico (including all fields), add `EKU9003173C9` as the :guilabel:`VAT` and `ESCUELA KEMPER URGATE` as the :guilabel:`Company Name`. For the :guilabel:`Fiscal Regime`, use :guilabel:`General de Ley Personas Morales`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:193 -msgid "All products to be sold need to have the SAT code associated with their classification so that the invoices do not give an error when validating." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:178 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:623 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:180 +msgid "To create a contact that can be invoiced, go to :menuselection:`Contacts --> Create`. Then enter the contact's name, full :guilabel:`Address` including :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and RFC (:guilabel:`VAT` number)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:185 +msgid "As with your own company, all of your contacts needs to have their correct business name registered in the |SAT|. This also applies to the :guilabel:`Fiscal Regime` which needs to be added in the :guilabel:`MX EDI` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:192 +msgid "Some additional configurations for factor type and tax objects need to be added to the sales taxes in order to properly sign invoices." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:196 -msgid "To configure products, go to the **General Information** tab and in the **UNSPSC Product Category** field select the category that represents that product. The process can be done manually or through a bulk import." +msgid "Factor type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:198 +msgid "Go to :menuselection:`Accounting --> Configuration --> Taxes` then enable the :guilabel:`Factor Type` field in the :guilabel:`Advanced Options` tab for all records with the :guilabel:`Tax Type` set as :guilabel:`Sales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:202 +msgid "This is pre-loaded in the default taxes. If new ones are created, you need to make sure to fill this field." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Configure products" +msgid "Taxes configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:205 -msgid "PAC Configuration to sign invoices" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:209 +msgid "Mexico manages two different kinds of 0% VAT: *0% VAT* and *VAT Exempt*. For the former, select the :guilabel:`Factor Type` :guilabel:`Tasa`. For the latter, use :guilabel:`Exento`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:207 -msgid "Another important step to configure electronic invoicing in Odoo is to enter the PAC which you are working with and the credentials. That way, electronic invoicing will be enabled." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:213 +msgid "Tax object" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:211 -msgid "Remember that you must register directly with the PAC of your choice before you start creating invoices from Odoo. We have the following PACs available: `Quadrum `_, `Solución Factible `_ and `SW Sapien - Smarter Web `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:215 +msgid "One requirement of the CFDI 4.0 is that the resulting XML file needs or does not need to break down the taxes of the operation. There are three different possible values that are added depending on specific configurations:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:216 -msgid "You must process your **Private Key (CSD)** with the SAT institution before following these steps. If you do not have this information, try with the Test Credentials and return to this process when you have the SAT Credentials for your production environment to work with real transactions." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:219 +msgid "`01`: Not subject to tax - your invoice must not contain any taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:220 +msgid "`02`: Subject to tax - your invoice contains taxes (default configuration)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:221 -msgid "To add the credentials, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the **PAC MX** section, enter the name of your PAC with your credentials (PAC username and PAC password)." +msgid "`03`: Subject to tax and not forced to breakdown - your invoice contains taxes, and the contact configuration has the :guilabel:`No Tax Breakdown` checkbox activated." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PAC credentials" +msgid "Tax Breakdown SAT." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:230 -msgid "If you check the checkbox **Test Environment**, it is not necessary to enter a PAC username and/or password, but you must select a PAC from the drop-down list." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:228 +msgid "The :guilabel:`No Tax Breakdown` value applies only to specific fiscal regimes and/or taxes. Consult your accountant first if it is needed for your business before doing any modification." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:233 -msgid "Finally, upload the digital certificates of the company within the section **MX Certificates**. Click on *Add a line*, a window will open, click on *Create* and from there you can upload your digital certificate, your key and your password. To finish, click on *Save and Close*." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:232 +msgid "Other tax configurations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:234 +msgid "When registering a payment, Odoo will carry out the movement of taxes from the *Cash Basis Transition Account* to the account set in the :guilabel:`Definition` tab. For such movement, a tax base account will be used: (`Base Imponible de Impuestos en Base a Flujo de Efectivo`) in the journal entry when reclassifying taxes. **Do not delete this account**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:239 +msgid "If you create a new tax, you need to add the correct :guilabel:`Tax Grids` for it (`IVA`, `ISR` or `IEPS`). Odoo only supports these three groups of taxes." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Certificate and key" +msgid "Taxes accounts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:242 -msgid "If you still do not have one of the contracted PACs and you want to test electronic invoicing you can use the following SAT test certificates:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:245 -msgid ":download:`Certificate `" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:246 -msgid ":download:`Certificate Key `" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:247 -msgid "**Password:** ``12345678a``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:249 -msgid "You must also configure the company with a real address within Mexico (including all fields) and add ``EKU9003173C9`` as the **VAT** number." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:248 +msgid "To configure products, go to the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product Category` field, select the category that represents that product. The process can be done manually or through :doc:`a bulk import `." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:253 -msgid "Workflows" +msgid "All products need to have a |SAT| code associated with them in order to prevent validation errors." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:256 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:257 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:303 msgid "Electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:258 -msgid "The invoicing process in Odoo is based on `Annex 20 `_ version 3.3 of electronic invoicing of the SAT." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:260 +msgid "PAC credentials" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:262 -msgid "To start invoicing from Odoo, an invoice must be created using the standard invoicing flow, that is, either from a sales order or from the invoice menu in the Accounting application." +msgid "After you have processed your `Private Key (CSD) `_ with the |SAT|, you must register directly with the :ref:`PAC ` of your choice before you start creating invoices from Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:265 -msgid "The invoice will be stamped after clicking on *Validate*, before that the status is still in draft mode and changes can be made to it. After validating the invoice, you can verify that it was successfully stamped, as it would look like this:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:267 +msgid "Once you created your account with any of these providers, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the :guilabel:`MX PAC` section, enter the name of your |PAC| with your credentials (:guilabel:`PAC username` and :guilabel:`PAC password`)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Creating an invoice" +msgid "PAC credentials." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:273 -msgid "The details of the invoice will be reflected in the Chatter, which is what you see on the right of the invoice in the attached image. There you can find your XML sent to the SAT and the status of the stamping, that is, if it was validated or not." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:275 +msgid "If you do not have credentials and want to test the electronic invoicing, you can activate the :guilabel:`Test Environment` checkbox and select :guilabel:`Solucion Factible` as the |PAC|. You do not need to add a username or password." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:277 -msgid "To send the stamped invoice to your client, you can send the XML together with the PDF file directly from Odoo, by clicking the *Send and Print* button. You can also download the PDF file directly to your computer by clicking the *Print* button and selecting the desired option." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:280 +msgid ".cer and .key certificates" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:282 -msgid "Depending on the size of the screen, the Chatter can be seen next to or below the document." +msgid "You need to upload the `digital certificates of the company `_ within the section :guilabel:`MX Certificates`. Select :guilabel:`Add a line` and a window will open. Click on :guilabel:`Create`, and from there upload your digital certificate (:file:`.cer` file), your key (:file:`.key` file), and your password. To finish, click on :guilabel:`Save and Close`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:285 -msgid "Invoicing Special Cases" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Certificate and key." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:288 -msgid "Foreign Trade Invoice" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:290 -msgid "The foreign trade invoicing process in Odoo is based on the corresponding `SAT regulation `_. SAT electronic invoicing version is 3.3." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:292 +msgid "If you still do not have one of the contracted |PAC|\\s and you want to test electronic invoicing you can use the following |SAT| test certificates:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:295 -msgid "What do we mean when we talk about foreign trade?" +msgid ":download:`Certificate `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:296 +msgid ":download:`Certificate Key `" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:297 -msgid "Since January 2018, the SAT requires a Foreign Trade Supplement in export transactions." +msgid "**Password**: ``12345678a``" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:300 -msgid "What is the Foreign Trade complement?" +msgid "Workflows" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:302 -msgid "It is an Annex to the electronic invoice that allows the identification of exporters and importers, in addition to expanding the description of the merchandise sold." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:305 +msgid "The invoicing process in Odoo is based on `Annex 20 `_ version 4.0 of electronic invoicing of the |SAT|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:306 -msgid "What information can be incorporated in this new complement?" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:308 -msgid "Information on the operation type it covers." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:309 -msgid "Tax identification data of the issuer, receiver or recipient of the merchandise." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:310 -msgid "Description of the goods to be exported." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:313 -msgid "Who is obliged to generate it?" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:312 +msgid "To start invoicing from Odoo, a customer invoice must be created using the :doc:`standard invoicing flow `." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:315 -msgid "Taxpayers who carry out export operations of A1 type." +msgid "When the document is in draft mode, you can make any changes to it (add the correct :guilabel:`Payment Way` or :guilabel:`Usage` that the customer might require, for example.)" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:318 -msgid "To which exports does the A1 type apply?" +msgid "After you :guilabel:`Confirm` the customer invoice, a blue message appears stating: :guilabel:`The invoice will be processed asynchronously by the following E-invoicing service: CFDI (4.0)`. Pressing the :guilabel:`Process Now` button sends the document to be signed by the government. On success, the :guilabel:`Fiscal Folio` field appears on the document and the XML file is attached in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:320 -msgid "Entry of goods of foreign origin to remain in national territory for an unlimited time." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:325 +msgid "If you press :guilabel:`Retry` in the field :guilabel:`SAT status` of the invoice, you can confirm if the XML file is valid in the SAT." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 -msgid "Exit of goods from the country to stay abroad for an unlimited time." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:328 +msgid "If you are in a testing environment, you will always receive the message :guilabel:`Not Found`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:322 -msgid "Definitive importation of vehicles by diplomatic and consular missions and offices of international organizations and their foreign personnel, in accordance with the import of vehicles in diplomatic exemption." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:327 -msgid "Is Foreign Trade the same as Pedimentos?" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:329 -msgid "Not necessarily, the Pedimentos are directly related to the process of Importing goods, while the Foreign Trade Complement is related to the Exporting process." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:333 -msgid "Required Modules" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:335 -msgid "In order to generate foreign trade invoices, the following modules must be installed." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:330 +msgid "To send the signed invoice to your client by mail, you can send the XML together with the PDF file directly from Odoo by clicking the :guilabel:`Send and Print` button. You can also download the PDF file to your computer by clicking the :guilabel:`Print` button and selecting the desired option." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:337 -msgid "EDI for Mexico (l10n_mx_edi)" +msgid "While an invoice is a document type \"I\" (Ingreso), a credit note is a document type \"E\" (Egreso)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "EDI para México" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:339 +msgid "The only addition to the :doc:`standard flow for credit notes ` is that, as a requirement of the SAT, there has to be a relation between a credit note and an invoice through the fiscal folio." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:343 -msgid "EDI for Mexico (l10n_mx_edi_extended)" +msgid "Because of this, the field :guilabel:`CFDI Origin` adds this relation with a `01|`, followed by the fiscal folio of the original invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "EDI Advanced Features" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Creating a credit note." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:350 -msgid "Company" +msgid "For the :guilabel:`CFDI Origin` field to be added automatically, use the button :guilabel:`Add Credit Note` from the invoice instead of creating it manually." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:352 -msgid "Configure the company with a valid postal code, and if you have a colony code, this should match with the corresponding Zip Code. At the same time, remember to place the Tax Identification Number (VAT Number - RFC)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:354 +msgid "Payment complements" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Contact address configuration" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:361 -msgid "Receiving Client" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:363 -msgid "Generally it will be a foreign client, in which you must verify that you have at least the following fields completed with the corresponding information." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "External trade invoice" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:371 -msgid "The customer's delivery address must also contain the zip code." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:372 -msgid "The format of the foreign VAT (Tax Identification Number) will be validated as appropriate in each Country (Example: Colombia ``123456789-1``)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:374 -msgid "In the XML, the VAT is automatically replaced by the Generic VAT for abroad transactions: ``XEXX010101000``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:380 -msgid "At the product level there must also configure some parameters in the following fields." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "SAT product code" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Tariff fraction" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:391 -msgid "You must select the **UMT Aduana** (Unit of Measure) in *KG* since it is only accepted by the SAT" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:392 -msgid "The weight refers to **the unit weight** of the product" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:393 -msgid "The tariff item must be from the code UoM of Kilograms (**UoM = 01**)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:395 -msgid "Although the product is sold in pieces or in units, the value that must be registered with customs in the tariff item must be reported in Kilograms." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:399 -msgid "Invoicing Flow" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:401 -msgid "When creating the foreign sales invoice, you must select the **Incoterm** corresponding and the **Need external trade?** checkbox must be checked. With this configuration enabled, the **PDF** and the complement **XML** of the invoice will have the necessary information to comply with the SAT regulations." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:407 -msgid "What is the certificate of origin and when is it used?" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:409 -msgid "The **Certificate Source** (or proof of origin) is the document that allows an importer or exporter to prove the country or region from which a good is considered to originate and serves to receive tariff preferences generally agreed in trade agreements." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Incoterm on invoice" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PDF external Trade" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:422 -msgid "Assign Pedimentos" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:424 -msgid "If your company imports products and you need to add the **Pedimentos** number in your invoices, you can also configure Odoo to record the process." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:427 -msgid "First, go to :menuselection:`Apps`, remove the \"Apps\" filter and search for ``Mexico``, ``mx`` or ``l10n_mx``. Then, install **Odoo Mexico Localization for Stock / Landing module (l10n_mx_edi_landing)**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "MX stock module" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:436 -msgid "The l10n_mx_edi_landing module depends on the **Inventory** and **Sales** apps, since the products must be entered into inventory to be able to add their Pedimentos number to the corresponding receipt of products." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:440 -msgid "Then, go to :menuselection:`Inventory --> Settings --> Settings`. Within the options, activate **Landed Costs**. This option will allow adding the Pedimentos number to the corresponding product receptions." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Costos en destino" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:449 -msgid "In order to use landed costs, the accounting configuration of the inventory valuation of the products must be configured as *Automated* and its costing method *Average* or *FIFO* (first in, first out)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:453 -msgid "To associate the Pedimentos number indicated with an import (merchandise reception) a new **Landed Cost** must be created. They can be accessed through :menuselection:`Inventory --> Operations --> Landed Costs`. There you will find the option to attach the Pedimentos number." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Customs number" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:462 -msgid "You can only add the Pedimentos number once, so be careful when associating the correct number with the transfer(s)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:466 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:469 -msgid "Payment Terms" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:471 -msgid "The **Payment Terms** are already configured in Odoo when installing the Mexican localization, this means that if you go to :menuselection:`Accounting --> Configuration --> Payment Terms`, you will find the default list in Odoo." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Payment terms" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:479 -msgid "In Mexico you can have 2 types of payments: PPD or PUE. These are given by the **Payment Term** chosen (or if there is no chosen payment term it will be based on the due date of the invoice)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:483 -msgid "PPD Payments" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:485 -msgid "To configure PPD payments (payment in installments or deferred) it is only necessary to choose a date expiration date for your invoice and Odoo will detect if it is after the first day of the following month (in this case no payment term is set - with the payment term you can also stipulate if it will be PPDo PUE)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:491 -msgid "PUE" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:493 -msgid "To configure PUE payments (payment in a single payment) you must select an invoice due date within the same month or choose a payment term that does not imply changing the due month (immediate payment, 15 days, 21 days, all falling within the current month)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:500 -msgid "`According to the SAT documentation `_, there may be 2 types of payments: **PUE** or **PPD**. In both cases the payment process in Odoo is the same, the difference of whether the payment is PUE or PPD lies in the payment term of the invoice - as indicated in the previous point in the **Payment Terms**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:506 -msgid "If the payment is a PPD type, Odoo will generate the corresponding payment complement automatically when you *Confirm* it. If the payment is PUE, the payment complement will not be generated. The type of payment is visible from the invoice in the field called **Payment Policy** and takes the invoice date and the due date as parameters." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:357 msgid "Payment policy" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:515 -msgid "When configuring the contacts that will be used when making payments, you must configure the banks in the **Accounting** tab, place both the Bank, Account Number and CLABE." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:359 +msgid "One of the additions of the Mexican Localization is the field :guilabel:`Payment Policy`. `According to the SAT documentation `_, there may be 2 types of payments:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:364 +msgid "`PUE` (Pago en una Sola Exhibición/Payment in a Single Exhibition)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:365 +msgid "`PPD` (Pago en Parcialidades o Diferido/Payment in Installements or Deferred)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:367 +msgid "The difference lies in the *Due Date* or *Payment Terms* of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:369 +msgid "To configure |PUE| invoices, you must select an invoice :guilabel:`Due Date` within the same month or choose a payment term that does not imply changing the due month (immediate payment, 15 days, 21 days, all falling within the current month)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Contact bank account" +msgid "Example of an invoice with the PUE requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 +msgid "Some :guilabel:`Payment Terms` are already installed by default. You can check them in :menuselection:`Accounting --> Configuration --> Payment Terms`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:380 +msgid "To configure |PPD| invoices, you need to choose a :guilabel:`Due Date` after the first day of the following month (this also applies if your :guilabel:`Payment Term` is due in the following month)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Example of an invoice with the PPD requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:387 +msgid "Because the |PPD| policy implies that an invoice is not going to get paid at the moment, the correct :guilabel:`Payment Way` for the |PPD| invoices is :guilabel:`99 - Por Definir` (To define)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:392 +msgid "Payment flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:394 +msgid "In both cases, the payment process in Odoo :doc:`is the same `, the main difference would be that payments related to |PPD| invoices trigger the creation of a document type \"P\" (Pago)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:398 +msgid "If a payment is related to a |PUE| invoice, it can be registered with the wizard and be associated with the corresponding invoice. Its status will be :guilabel:`In Payment` since the payment is effectively validated when it is bank reconciled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:405 +msgid "While this process is the same for PPD invoices, the addition of the creation of an :doc:`electronic document ` means that some additional requirements are needed to correctly send the document to the SAT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:409 +msgid "You need to confirm the specific :guilabel:`Payment Way` where you received the payment. Because of this, this field cannot be :guilabel:`99 - Por Definir` (To Define)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:411 +msgid "If you are going to add a bank account to the customer in the :guilabel:`Accounting` tab of their contact, it needs to have a valid number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:415 +msgid "The exact configurations are in the `Anexo 20 of the SAT `_. Usually, the :guilabel:`Bank Account` needs to be 10 or 18 digits for transfers, 16 for credit or debit cards." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:419 +msgid "If a payment is related to a signed invoice with the :guilabel:`Payment Policy` `PPD`, Odoo generates the corresponding payment complement automatically once you press :guilabel:`Process Now`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "CFDI (4.0) E-invoicing service process payment now message." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:426 +msgid "A payment in MXN cannot be used to pay multiple invoices in USD. Rather, the payment should be separated into multiple payments created using the :guilabel:`Register Payment` button on the corresponding invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:431 +msgid "Invoice cancellations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:433 +msgid "It is possible to cancel the EDI documents sent to the SAT. According to the `Reforma Fiscal 2022 `_, since January 1st 2022, there are two requirements for this:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:437 +msgid "With all cancellation requests, you have to specify a *cancellation reason*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:438 +msgid "After 24 hours have passed, the client must be asked to accept the cancellation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:440 +msgid "There are four different cancellation reasons. In Odoo, you can cancel invoices with the reasons *01 Invoices sent with errors with a relation*, and *02 Invoices sent with errors without a relation*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:444 +msgid "01 - invoices sent with errors with a relation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:446 +msgid "This cancellation motive has to be used when a new invoice needs to substitute the original one, due to an error in any field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:449 +msgid "Copy the :guilabel:`Fiscal Folio` of the *old invoice*" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:450 +msgid "Paste it into the field :guilabel:`CFDI Origin` of the *new invoice*, followed by a `04|`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:451 +msgid "Sign the new document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Old invoice with CFDI Origin." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:456 +msgid "Go back to the *old invoice*, the field :guilabel:`Substituted By` should appear." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:457 +msgid "Click the :guilabel:`Request EDI Cancellation` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:458 +msgid "As if it were a regular invoice, a blue field then appears on the invoice. Click :guilabel:`Process Now`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:460 +msgid "The invoice status is moved to :guilabel:`Cancelled` and you receive a confirmation in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Invoice 01 properly canceled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:466 +msgid "Now, the invoice should be canceled in the SAT too. You can confirm that this was done correctly by pressing :guilabel:`Retry` in the SAT status field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:469 +msgid "If the document was canceled after 24 hours, it is possible that the client must be asked to accept the cancellation in their \"Buzón Tributario\"." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:473 +msgid "The `04|` is only a code that helps Odoo to perform this process. It has no relation to the method 04 reason for cancellation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:477 +msgid "02 - invoices sent with errors without a relation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:479 +msgid "This cancellation motive has to be used when an invoice was sent with an error in any field and does not need to be replaced by another one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:482 +msgid "For this case, all that is required is to click on :guilabel:`Request EDI Cancellation`, and then press click the :guilabel:`Process Now` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Invoice 02 properly canceled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:488 +msgid "As the field :guilabel:`Substituted By` does not exist, the SAT should detect automatically that the cancellation reason is 02." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:492 +msgid "Odoo has certain limitations to canceling invoices in the SAT: The reasons 03 and 04 (*Operation did not take place* and *Nominative transactions related to a global invoice*) are not currently supported by Odoo. For this, you need to cancel the invoice directly in the SAT and use a *Server Action*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:498 +msgid "Payment cancellations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:500 +msgid "It is also possible to cancel *Payment Complements*. For this, go to the payment and select :guilabel:`Request EDI Cancellation`. As with invoices, a blue button will appear. Select :guilabel:`Process now`, and the document will be sent to the SAT. After a few seconds, you can press :guilabel:`Retry` to confirm the current SAT status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:505 +msgid "The payment moves their status to :guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:508 +msgid "Just like invoices, when you create a new *Payment Complement*, you can add the relation of the original document by adding a `04|` plus the fiscal folio." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:512 +msgid "Invoicing special use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:515 +msgid "CFDI to public" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:517 +msgid "If the customer you are selling goods or services to does not require an invoice, a *CFDI to Public* has to be created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:520 +msgid "However, if you use the name `PUBLICO EN GENERAL`, an error will be triggered. This is a main change in the CFDI 4.0 that states that invoices with that specific name needs additional fields." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:523 -msgid "Register PPD Payments" +msgid "Odoo currently does not support this. So for a *CFDI to Public* to be created, you need to add any name to your customer that is not `PUBLICO EN GENERAL`. (For example `CLIENTE FINAL`)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:525 -msgid "If at the time of registering a payment it is of type PPD then a Payment Complement (XML) will be generated with its details." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:528 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:573 -msgid "The payment can be registered from the invoice and once it is confirmed, the invoice will be paid and with its payment associated." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:526 +msgid "In addition to this, the zip code of your company, and the generic :guilabel:`RFC` ``XAXX010101000`` are needed. The :guilabel:`Fiscal Regime` of your customer must be `Sin obligaciones fiscales`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PPD payments" +msgid "CFDI to Public Error." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PPD payment information" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:535 +msgid "The main currency in Mexico is MXN. While this is mandatory for all Mexican companies, it is possible to send and receive invoices and payments in different currencies. To do this, you can enable the use of :doc:`multicurrency `. And select :guilabel:`Mexican Bank` as the service in :menuselection:`Accounting --> Settings --> Currency`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:540 -msgid "The journal will be the payment method where you receive or send the payment from. You must also associate a **Payment Way** and a Recipient Bank Account (this last one must be created within the contact associated with the invoice)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:541 +msgid "This way, in the XML file of the document you get the correct exchange rate and the total amount both in the foreign currency and in MXN." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:544 -msgid "Once the payment is made, it will be associated with the corresponding invoice and its status will be *In Payment* since the payment will be effectively validated when it is bank reconciled." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:548 -msgid ":doc:`../accounting/bank/reconciliation`." +msgid "It is highly recommended to use :doc:`a bank account for each currency `." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PPD payment created" +msgid "Multi-currency configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:551 +msgid "The only currencies that automatically update their exchange rate daily are USD, EUR, GBP, and JPY." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:555 -msgid "The **Recipient Bank Account** is the one attached to the **Accounting** tab in the contact associated with the invoice, it must be valid so that the stamped payment complement can be created." +msgid "Down payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:560 -msgid "When making a payment in MXN for an invoice in USD, the payment must be created using the :guilabel:`Register Payment` button **on the invoice view** and not separately as a payment. Otherwise, the payment CFDI is not correctly generated." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:557 +msgid "There can be cases where you receive a payment in advance from a customer, that needs to be applied to an invoice later. In order to do this in Odoo, it is required to properly link invoices to each other with the :guilabel:`CFDI Origin` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:563 -msgid "As such, a payment in MXN cannot be used to pay multiple invoices in USD. Rather, the payment should be separated into multiple payments created using the :guilabel:`Register Payment` button on the corresponding invoices." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:561 +msgid "It is necessary to have the :doc:`Sales ` app installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:568 -msgid "Register PUE Payments" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:570 -msgid "If at the time of registering a payment it is of the PUE type then in this case a Payment Complement (XML) will not be generated since it is not necessary." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PUE payments" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PUE payment information" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PUE payment created" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:589 -msgid "In this case it is not created as a payment supplement by the nature of it." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:592 -msgid "Down Payments" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:594 -msgid "This is a special case in which we must receive an advance payment from a client to later be applied to an invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:598 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:564 msgid "`The official documentation for registration of down payments in Mexico `_." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:567 +msgid "First, navigate to the :menuselection:`Sales` app to create a product `Anticipo` and configure it: the :guilabel:`Product Type` must be :guilabel:`Service`, and use the :guilabel:`UNSPSC Category` `84111506 Servicios de facturación`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:571 +msgid "Then, go to :menuselection:`Sales --> Settings --> Invoicing --> Down Payments` and add the product as the default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:574 +msgid "Create a sales order with the total amount, and create a down payment (either using a percentage or fixed amount). Then, sign the document, and :guilabel:`Register the Payment`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:577 +msgid "When the time comes for the customer to get the final invoice, create it again from the same sales order. In the :guilabel:`Create Invoices` wizard select :guilabel:`Regular Invoice` and uncheck :guilabel:`Deduct down payments`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:581 +msgid "Then, copy the :guilabel:`Fiscal Folio` from the first invoice and paste it into the :guilabel:`CDFI Origin` of the second invoice, adding the prefix `07|`. Sign the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:584 +msgid "After this, create a credit note for the first invoice. Copy the :guilabel:`Fiscal Folio` from the second invoice and paste it in the :guilabel:`CFDI Origin` of the credit note, adding the prefix `07|`. Sign the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:588 +msgid "With this, all electronic documents are linked to each other. The final step is to fully pay the new invoice. At the bottom of the new invoice, you can find :guilabel:`Outstanding credits` in the credit note, add it as payment. Finally, register the remaining amount with the :guilabel:`Register Payment` wizard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:594 +msgid "External trade" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:596 +msgid "The external trade is a complement to a regular invoice that adds certain values in both the XML and PDF, according to `SAT regulations `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:600 +msgid "This adds certain mandatory fields to invoices with a foreign customer, such as:" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/mexico.rst:602 -msgid "Process to create advance in Mexico" +msgid "The specific address of the receiver and the sender" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:603 +msgid "The addition of a :guilabel:`Tariff Fraction` that identifies the type of product" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:604 -msgid "Issuance of electronic invoicing with the amount of the advance payment received." +msgid "The correct :guilabel:`Incoterm` (International Commercial Terms), among others." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:605 -msgid "Issuance of the electronic invoice for the total value of the operation (full invoice). (CFDI Origin: 07 | Advance invoice, point 1)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:606 +msgid "This allows the correct identification of exporters and importers, in addition to expanding the description of the merchandise sold." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:607 -msgid "Issuance of the electronic invoice with the *Egreso* type. (CFDI Origin: 07 | Invoice_total, point 2)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:609 +msgid "Since January 1st, 2018, it is a requirement for taxpayers who carry export operations of A1 type. While the current CFDI is 4.0, the external trade is currently on version 1.1" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:611 -msgid "Steps to follow in Odoo" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:613 -msgid "Preparation: Create the product" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:614 -msgid "Down Payment issuance of the electronic invoice for the amount of the advance payment received" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:615 -msgid "Issuance of the electronic invoice for the total value of the operation" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:612 +msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended` and :guilabel:`l10n_mx_edi_extended_40` have to be installed." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:616 -msgid "Add a credit note from the down payment invoice" +msgid "Before installing, make sure first that your business needs to use this feature. Consult your accountant first if needed before doing any modification." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:619 -msgid "Preparation: Create the Product" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:625 +msgid "While the CFDI 4.0 requirements ask you to add a valid zip code in your contact, the external trade complement adds as a mandatory field the :guilabel:`City` and the :guilabel:`State`. All three fields must coincide with the `Official SAT Catalog `_ or you will receive an error." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:621 -msgid "The Down Payment product must be type *Service* and must use the **NSPSC Product Category**: *84111506 Servicios de facturación*." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:630 +msgid "Add the :guilabel:`City` and :guilabel:`State` in the company's contract, not in the company itself. You can find your company's contact in :menuselection:`Accounting --> Customers --> Customers`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:634 +msgid "The fields :guilabel:`Locality` and :guilabel:`Colony Code` are optional and can be added in the company directly in :menuselection:`Settings --> General Settings --> Companies`. These two have to coincide with the data in the SAT." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Down payment product" +msgid "Optional External Trade Company fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:628 -msgid "Add the down payment product as default to be used from the Odoo configurations." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Down payment configuration" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:635 -msgid "Issuance of the electronic invoice for the value of the advance received" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:637 -msgid "Create the Advance Payment Invoice: From the sales order, create an advance payment invoice for the percentage of the purchase to be paid in advance (or for a fixed amount)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Applying down payment" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:641 +msgid "The contact data for the foreign receiving client must have the following fields completed to avoid errors:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:644 -msgid "Validate invoice with the down payment product." +msgid "The entire company :guilabel:`Address`, including a valid :guilabel:`ZIP` code and the foreign :guilabel:`Country`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:646 +msgid "The format of the foreign :guilabel:`VAT` (tax identification number, for example: Colombia `123456789-1`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:648 +msgid "In the :guilabel:`MX EDI` tab, you need to address if the customer receives goods for a period of time temporarily (:guilabel:`Temporary`) or permanently (:guilabel:`Definitive`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:650 +msgid "If you create this contact based in another from Mexico, make sure that you delete any information in the field :guilabel:`Fiscal Regime`. Do not use :guilabel:`No Tax Breakdown` either." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Confirm down payment" +msgid "Required External Trade Customer fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Folio fiscal down payment" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:658 +msgid "In the resulting XML and PDF, the :guilabel:`VAT` is automatically replaced by the generic VAT for abroad transactions: `XEXX010101000`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:654 -msgid "Register Payment to the advance payment invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Down payment invoice" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Down payment registered" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:665 -msgid "Issuance of the electronic invoice for the total value of the operation." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:664 +msgid "All products involved with external trade must fill four fields, two of them exclusive to this feature." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:667 -msgid "From the sales order, create an invoice for the total, that is, for all the order lines without discounting the advance." +msgid "The :guilabel:`Internal Reference` of the product is in the :guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:668 +msgid "The :guilabel:`Weight` of the product must be more than `0`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:669 +msgid "The `correct `_ :guilabel:`Tariff Fraction` of the product in the :guilabel:`Accounting` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:671 +msgid "The :guilabel:`UMT Aduana` corresponds to the :guilabel:`Tariff Fraction`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Full invoice" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:675 -msgid "Remove the check mark from the **Deduct down payments** field." +msgid "Required External Trade Product fields." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:677 -msgid "Add the original CFDI of the advance payment invoice by adding ``07 |`` at the beginning + Folio Fiscal of the advance payment Invoice created in the previous step." +msgid "If the UoM code of the :guilabel:`Tariff Fraction` is `01`, the correct :guilabel:`UMT Aduana` is `kg`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:680 -msgid "Copy the Folio Fiscal of the following invoice following this example:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:679 +msgid "If the UoM code of the :guilabel:`Tariff Fraction` is `06`, the correct :guilabel:`UMT Aduana` is `Units`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:683 +msgid "Invoicing flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:685 +msgid "Before creating an invoice, it is important to take into account that external trade invoices require to convert the amounts of your product into USD. Therefore, we need to have :doc:`multicurrency enabled ` and activate USD in the :guilabel:`Currencies` section. The correct :guilabel:`Service` to run is :guilabel:`Mexican Bank`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:691 +msgid "With the correct exchange rate set up in :menuselection:`Accounting --> Settings --> Currency`, the only fields left are :guilabel:`Incoterm` and :guilabel:`Certificate Source` in the :guilabel:`Other Info` tab. The latter is optional." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Folio full invoice" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:686 -msgid "And paste it in the draft invoice created from the Sales Order without deducting the advances:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "CFDI origen folio" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:692 -msgid "Validate and copy the Folio Fiscal for later (in the example the Folio Fiscal copy is: 50E4FF06-4341-4006-A7C3-A7F653CBEFAE )" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:696 -msgid "Add credit note from invoice" +msgid "External Trade Other Info." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:698 -msgid "Create a **Credit Note** from the down payment invoice (the corrective invoice must be edited prior to confirming it, see explanation below the 2 following images)" +msgid "Sign the invoice with the same process as a regular one: Press the :guilabel:`Process Now` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Creation of a Credit Note" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:701 +msgid "Delivery guide" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Matching down payment" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:703 +msgid "A `Carta Porte `_ is a bill of lading: a document that states the type, quantity, and destination of goods being carried." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:709 -msgid "Before you *Confirm* the Credit Note, edit the Origin CFDI with ``07 | XXX`` instead of the prefix ``01 | XXX``" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:706 +msgid "On December 1st, 2021, version 2.0 of this CFDI was implemented for all transportation providers, intermediaries, and owners of goods. Odoo is able to generate a document type \"T\" (Traslado) which, unlike other documents, is created in a delivery order instead of an invoice or payment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Modify folio fiscal" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:710 +msgid "Odoo can create XML and PDF files with or without ground transport and can process materials that are treated as *Dangerous Hazards*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "CFDI origen type" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:713 +msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended`, :guilabel:`l10n_mx_edi_extended_40`, :guilabel:`l10n_mx_edi_stock` and :guilabel:`l10n_mx_edi_stock_40` have to be installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:720 -msgid "Now the invoice can be confirmed." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:717 +msgid "In addition to this, it is necessary to have the :doc:`Inventory ` and :doc:`Sales ` apps configured." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Post credit note" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:722 +msgid "Odoo does not support Carta Porte type \"I\" (Ingreso), air, or marine transport. Consult your accountant first if this feature is needed before doing any modifications." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:726 -msgid "Now the Credit Note (Advance Payment) must be applied to the total invoice, this is added at the bottom below the amount owed." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:728 +msgid "Odoo manages two different types of CFDI:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Add credit note" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:730 +msgid "**No Federal Highways**: It is used when the *Distance to Destination* is `less than 30 KM `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Down payment applied" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:732 +msgid "**Federal Transport**: It is used when the *Distance to Destination* exceeds 30 KM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:734 +msgid "Other than the standard requirements of regular invoicing (The RFC of the customer, the UNSPSC code...), if you are using *No Federal Highways*, no external configuration is needed." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:737 -msgid "Register a payment for the difference of the down payment and the total of the sale." +msgid "For *Federal Transport*, several configurations have to be added to contacts, vehicle setups, and products. Those configurations are added to the XML and PDF files." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Residual amount payment" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:741 +msgid "Contacts and vehicles" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:743 -msgid "If you go to the XML of the invoice, you should see in CFDI related the type of relationship 07 and the Folio Fiscal of the advance payment invoice." +msgid "Like with the external trade feature, the address in both your company and your final customer has to be complete. The zip code, city, and state must coincide with the `Official SAT Catalog `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:748 +msgid "The field :guilabel:`Locality` is optional for both addresses." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "XML down payment" +msgid "Delivery Guide Contacts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:751 -msgid "Discounts based on payment days" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:753 -msgid "Cash discounts are incentives that you can offer to motivate customers to pay within a specified time period. For example, you offer a 2% discount if the customer pays you within the first 5 days of the invoice, when it is due in 30 days. This approach can greatly improve your average customer payments period." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:754 +msgid "The origin address used for the delivery guide is set in :menuselection:`Inventory --> Configuration --> Warehouses Management --> Warehouses`. While this is set as the company address by default, you can change it according to your correct warehouse address." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:758 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:763 -msgid "Create and assign the corresponding Payment Term" +msgid "Another addition to this feature is the :guilabel:`Vehicle Setups` menu found in :menuselection:`Inventory --> Settings --> Mexico`. This menu lets you add all the information related to the vehicle used for the delivery order." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:759 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:782 -msgid "Register the Payment within the days of the discount" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:760 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:808 -msgid "Create a credit note" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:765 -msgid "To configure the discount for advance payment, go to :menuselection:`Accounting --> Configuration --> Payment Terms` and click on *Create*. Add a Percentage type with a corresponding value (for example, 98% of the total price for a 2% discount) and the number of days for which the offer is valid (for example 5 days). You can also change the balance due type if necessary (in this example 30 days)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:762 +msgid "All fields are mandatory to create a correct delivery guide." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Discount payment term" +msgid "Delivery Guide Vehicle Configurations required fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:775 -msgid "Then when creating our Sales Order or Sales Invoice, assign the Payment Term created previously." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:767 +msgid "In the :guilabel:`Intermediaries` section, you need to add the operator of the vehicle. The only mandatory fields for this contact are the :guilabel:`VAT` and :guilabel:`Operator Licence`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:773 +msgid "Like with regular invoicing, all products must have a :guilabel:`UNSPSC category`. In addition to this, there are two extra configurations for products involved in delivery guides:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:776 +msgid "The :guilabel:`Product Type` must be set as :guilabel:`Storable Product` for stock movements to be created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:778 +msgid "In the :guilabel:`Inventory` tab, the field :guilabel:`Weight` should have more than 0." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "discount on invoice" +msgid "Delivery Guide Product Configurations." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:784 -msgid "Register the payment within the days in which the application of the discount was specified, in our case it is within 5 days after the creation of the Sales Invoice." +msgid "Sales and inventory flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:786 +msgid "To create a delivery guide, first, you need to create and confirm a sales order. This generates a :guilabel:`Delivery` smart button. Press it and :guilabel:`Validate` the transfer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:789 +msgid "After the status is set to :guilabel:`Done`, you can edit the transfer and select the :guilabel:`Transport Type` (either :guilabel:`No Federal Highways` or :guilabel:`Federal Transport`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:793 +msgid "If your delivery guide has the type :guilabel:`No Federal Highways`, you can save the transfer and then press :guilabel:`Generate Delivery Guide`. The resulting XML can be found in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:797 +msgid "Other than the :guilabel:`UNSPSC` in all products, delivery guides that use :guilabel:`No Federal Highways` do not require any special configuration to be sent to the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:800 +msgid "If your delivery guide has the type :guilabel:`Federal Transport`, the tab :guilabel:`MX EDI` appears. In there, write a value in :guilabel:`Distance to Destination (KM)` bigger than `0`, and select the :guilabel:`Vehicle Setup` used for this delivery." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Discount payment" +msgid "Delivery Guide MX EDI tab configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:791 -msgid "Then go to the bottom of the invoice where the totals are located and there you will see 2 payments created, reset to draft and cancel the payment that does not correspond - the one related to the discount." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "See discount payment" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Mote to draft payment" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Cancel payment" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:808 +msgid "Dangerous hazards" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:810 -msgid "Finally to close the cycle we must close the invoice, but as in this case we apply a discount, to close it correctly we must create a credit note specifying that the difference was given to the customer on a **Credit Note**." +msgid "Certain values in the :guilabel:`UNSPSC Category` are considered in the `official SAT catalog `_ as dangerous hazards. These categories need additional considerations when creating a delivery guide with :guilabel:`Federal Transport`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:815 +msgid "In the product, the fields :guilabel:`Hazardous Material Designation Code (MX)` and :guilabel:`Hazardous Packaging (MX)` must be filled with the correct code from the |SAT| catalog." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:818 +msgid "In the vehicle setup, the data from the :guilabel:`Environment Insurer` and :guilabel:`Environment Insurance Policy` has to be filed too." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Discount credit note" +msgid "Delivery Guide environment required fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Reason of credit note" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:824 +msgid "After this, continue with the regular process to create a delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:822 -msgid "Adjust the amount to the remaining balance in the original invoice." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:827 +msgid "Customs numbers" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Total credit note" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:829 +msgid "A *customs declaration* (Pedimento Aduanero) is a fiscal document that certifies that all contributions to the fiscal entity (the |SAT|) has been paid, for the import/export of goods." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:828 -msgid "Add the Credit Note to the original invoice so that it is settled." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:832 +msgid "According to the `Annex 20 `_ of CFDI 4.0, in documents where the invoiced goods come from a first-hand import operation, the field :guilabel:`Customs Number` needs to be added to all lines of products involved with the operation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Add credit note for discount" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:836 +msgid "For this, the module :guilabel:`l10n_mx_edi_landing` has to be installed, in addition to the :doc:`Inventory `, :doc:`Purchase ` and :doc:`Sales ` apps configured." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:835 -msgid "Cancellation of invoices" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:838 -msgid "Before 72 Hours" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:840 -msgid "If it is necessary to cancel an invoice validated and sent to the SAT in less than 72 hours follow the steps below." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:843 -msgid "Request Cancellation" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "Cancel within 72 hours" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:842 +msgid "Do not confuse this feature with external trade. The customs numbers are directly related to importing goods, while the external trade complement is related to exporting. Consult your accountant first if this feature is needed before doing any modifications." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:849 -msgid "The status of the **Electronic invoicing** changes to *Cancelled*" +msgid "In order to track the correct customs number for a specific invoice, Odoo uses :doc:`landed costs `. Go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation`. Make sure that :guilabel:`Landed Costs` is activated." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:850 -msgid "Click on *RESET TO DRAFT*" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:854 +msgid "First, a *service*-type product called `Pedimento` has to be created. In the :guilabel:`Purchase` tab, check :guilabel:`Is a Landed Cost` and select a :guilabel:`Default Split Method`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "Invoice to draft" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:857 +msgid "After this, we need to configure the *storable products* that holds the customs numbers. We need to make sure that the product category has the following configuration:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:856 -msgid "Click on *CANCEL ENTRY*" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:860 +msgid ":guilabel:`Costing Method`: Either :guilabel:`FIFO` or :guilabel:`AVCO`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "Cancel journal entry" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:861 +msgid ":guilabel:`Inventory Valuation`: :guilabel:`Automated`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:862 +msgid ":guilabel:`Stock Valuation Account`: :guilabel:`115.01.01 Inventario`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:863 -msgid "After 72 Hours" +msgid ":guilabel:`Stock Journal`: :guilabel:`Inventory Valuation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:864 +msgid ":guilabel:`Stock Input Account`: :guilabel:`115.05.01 Mercancías en tránsito`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:865 -msgid "If It is necessary to cancel an invoice validated and sent to the SAT more than 72 hours, the client must be asked to accept the cancellation, for this the following steps must be followed." +msgid ":guilabel:`Stock Output Account`: :guilabel:`115.05.01 Mercancías en tránsito`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:868 -msgid "Click on *Request EDI Cancellation* to inform the SAT that you want to cancel the invoice, in this case the client has to enter the SAT webpage and approve it. (The status of the **Electronic invoicing** field in Odoo changes to *To Cancel*)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Storable products configurations." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:871 -msgid "When the client (Receiver / Customer) approves the Cancellation in their SAT portal it is now possible to Change the invoice to Draft and then click on *Cancel entry*." +msgid "Purchase and sales flow" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:873 -msgid "Odoo synchronizes with the SAT to update the status of the **Electronic invoicing** with a scheduled action, Invoices canceled in the SAT will be canceled in Odoo." +msgid "Create a :guilabel:`Purchase Order`, and confirm the order. This should trigger a :guilabel:`Receipt` smart button. Validate the receipt too." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Cancel after 72 hours" +msgid "Customs Number Purchase." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:880 -msgid "After clicking on **Request EDI cancellation**, the status of the **Electronic invoicing** field will be *To Cancel* but the status of the SAT will be the same to *Valid*, it will remain active until the end customer / Recipient approves the cancellation in the SAT." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:879 +msgid "Go to :menuselection:`Inventory --> Operations --> Landed Costs` and create a new record. Add the transfer that you just created, and both the product `Pedimento` and :guilabel:`Customs number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:882 +msgid "Optionally, you can add a cost amount. After this, validate the landed cost. Once :guilabel:`Posted`, all products related to that receipt have the customs number assigned." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:886 +msgid "You can only add the Pedimentos number once, so be careful when associating the correct number with the transfer(s)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Check estado del PAC" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:888 -msgid "Once canceled in the SAT, Odoo will synchronize the status of the SAT through scheduled actions that are executed every day to synchronize the statuses of the SAT, Electronic invoicing and Odoo (this scheduled action can be executed manually by entering with developer mode)." +msgid "Customs number Inventory." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:892 -msgid "If the invoice is canceled in the SAT, in Odoo it is also canceled, which allows you to switch the invoice to draft and finally cancel the invoice (*cancel entry*)." +msgid "Now, create a sales order and confirm it. This should trigger a :guilabel:`Delivery` smart button. Validate it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:895 +msgid "Finally, create an invoice from the sales order and confirm it. The invoice line related to your product has a customs number in it." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PAC scheduled action" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:900 -msgid "Cancel Paid Invoices" +msgid "Customs number on confirmed sales order product." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:902 -msgid "If the invoice has already been paid, a credit note must be created from the invoice so that the originating CFDI is recognized and later cancel the original invoice." +msgid "Electronic accounting" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Cancel paid invoice" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:904 +msgid "For Mexico, `Electronic Accounting `_ refers to the obligation to keep accounting records and entries through electronic means and to enter accounting information on a monthly basis through the SAT's website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Credit note to cancel" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:909 +msgid "It consists of three main XML files:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:914 -msgid "Cancel Invoices from the previous period" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:911 +msgid "The updated list of the chart of accounts that you are currently using." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:917 -msgid "Problem" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:912 +msgid "A monthly trial balance, plus a closing entry report also known as *Trial Balance Month 13*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:913 +msgid "Either optional or for a compulsory audit, an export of the journal entries in your general ledger." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:916 +msgid "The resulting XML files follow the requirements of the `Anexo Técnico de Contabilidad Electrónica 1.3 `_." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:919 -msgid "If the invoice is from the previous month and the period is closed, the income has already been declared in Financial Reports and to the government. In Odoo, when canceling an invoice, the journal entry is eliminated as if the income already reported had not existed, this represents a fiscal problem because the income was already declared in the previous month." +msgid "In addition to this, you can generate the `DIOT `_: A report of vendor's journal entries that involves IVA taxes that can be exported in :file:`.txt` file." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 -msgid "The problem resides when the fiscal period has been closed, in the current period you have to make the reverse entry and save the cancellation information." +msgid "In order to use these reports, the modules :guilabel:`l10n_mx_reports`, :guilabel:`l10n_mx_reports_closing`, :guilabel:`l10n_mx_xml_polizas` and :guilabel:`l10n_mx_xml_polizas_edi` have to be installed, as well as the :doc:`Accounting `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:927 -msgid "Invoice to be canceled" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:929 +msgid "You can find all of those reports in :menuselection:`Accounting --> Reporting --> Mexico`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Previous period" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:932 +msgid "The specific characteristics and obligations of the reports that you send might change according to your fiscal regime. Always contact your accountant before sending any documents to the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:933 -msgid "This is how the Balance Sheet looks like:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Previous BS" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:937 +msgid "Catálogo de cuentas (chart of accounts)" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:939 -msgid "If the invoice is canceled, the journal entry and the Balance Sheet looks like this after canceling:" +msgid "The :doc:`chart of accounts ` in México follows a specific pattern based in SAT's `Código agrupador de cuentas `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "AR in BS" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:943 +msgid "You can create any account as long as it respects |SAT|'s encoding group, This pattern is `NNN.YY.ZZ` or `NNN.YY.ZZZ`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:946 -msgid "Solution" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:948 -msgid "Close the fiscal period every month (Best Practice Mexican Localization)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:947 +msgid "Some examples are `102.01.99` or `401.01.001`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:949 -msgid "Cancel invoice in SAT" +msgid "When you create a new account in :menuselection:`Accounting --> Configuration --> Chart of Accounts`, if you follow this pattern, you get the correct grouping code in :guilabel:`Tags`, and your account appears in the COA report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:950 -msgid "Create a Manual Reversion entry (Journal Entry)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:953 +msgid "Once you created all your accounts, and made sure that you put the correct :guilabel:`Tags` in them." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:951 -msgid "Reconcile the open invoice with the reversal entry (Journal Entry)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:956 +msgid "You cannot use any pattern that ends a section with a 0 (such as `100.01.01`, `301.00.003` or `604.77.00`). This triggers errors in the report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:952 -msgid "Change Electronic invoicing status to Cancelled with server action" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:959 +msgid "Once all is set up, you can go to :menuselection:`Accounting --> Reporting --> Mexico --> COA` and press the button :guilabel:`SAT (XML)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:955 -msgid "Close accounting period each month (Best Practice Mexican Localization)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:957 -msgid "If the accounting period is closed due to the blocking dates, Odoo will not allow to modify or add accounting entries of a date corresponding to that accounting period." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Closing fiscal period" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:963 +msgid "Balanza de comprobación (trial balance)" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:965 -msgid "Cancel invoice in the SAT" +msgid "The trial balance reports the initial balance, credit, and total balance of your accounts, provided that you added their correct encoding group." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:967 -msgid "If the accounting period is closed, and the invoice was canceled in the SAT, the status in Odoo will be published while the **Electronic invoicing** status will be *Sent* and the SAT status is *Cancelled*." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:968 +msgid "This report can be generated monthly, and an XML file version is created if you go to :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance` and press the button :guilabel:`SAT (XML)`. Select the month you want to download beforehand." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Cancel in SAT" +msgid "Trial Balance Report." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:976 -msgid "Create Manual Reversal Journal Entry" +msgid "Odoo does not generate the *Balanza de Comprobación Complementaria*." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:978 -msgid "The solution is to create the reversal journal entry manually dated in the current fiscal period and reconcile the open invoice with the reversion created manually." +msgid "An additional report is the *Month 13*: a closing balance sheet that shows any adjustments or movements made in the accounting to close the year." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:981 -msgid "It must be clearly indicated in the reference that it is a cancellation (you can use a cancellation account for invoices from previous periods such as **Other Income**)." +msgid "In order to be able to generate this XML document, you have to go to :menuselection:`Accounting --> Accounting --> Miscellaneous --> Journal Entries` and create a new document. Here, you can add all amounts that you want to modify, and you can balance the debit and/or credit of each one." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Manual reversal" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:985 +msgid "After this is done, press :guilabel:`Mark as Closing Entry`, and the report found in :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance Month 13` contains the total amount of the year, plus all the additions of the journal entry." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:989 -msgid "Reconcile the open invoice with the reversal entry" +msgid "You can generate the XML file by pressing the button :guilabel:`SAT (XML)`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Reconcile open invoice" +msgid "Trial Balance Month 13 Setup." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:995 +msgid "Pólizas (general ledger)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:997 +msgid "By law, all transactions in Mexico must be recorded digitally. Because Odoo automatically creates all the underlying journal entries of your invoicing and payments, you can export your journal entries to comply with SAT's audits or tax refunds." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1001 +msgid "This XML file is created in :menuselection:`Accounting --> Reporting --> Audit Reports --> General Ledger`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1005 +msgid "You can filter by period or by journal, according to your current needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1007 +msgid "After you press :guilabel:`XML (Polizas)`, a wizard appears. In here, you can select between four types of :guilabel:`Export type`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1010 +msgid "For :guilabel:`Tax audit` or :guilabel:`Audit certification`, you need to write the :guilabel:`Order Number` provided by the |SAT| for :guilabel:`Return of goods` or :guilabel:`Compensation`, you need to write your :guilabel:`Process Number`, also provided by the |SAT|." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Open invoice paid" +msgid "Types of Polizas." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:999 -msgid "In the Balance Sheet and Trial balance they are now with the correct balances." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1018 +msgid "If you want to see this report without sending it, use `ABC6987654/99` for :guilabel:`Order Number` and `AB123451234512` for :guilabel:`Process Number`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "New BS" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Up to date BS" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Balanza de comprobación" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1014 -msgid "Change status of Electronic invoicing to Cancelled with server action" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1016 -msgid "A server action can be created that modifies the status of the invoice to *Cancelled* once it is reconciled with the reversal entry (You should check this with support or with your Assigned Functional Consultant prior to performing this action)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Scheduled action PAC status" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Execute server action" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1029 -msgid "Electronic Accounting" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1031 -msgid "Accounting for Mexico in Odoo is composed of 3 reports:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1033 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1047 -msgid "Electronic Chart of Accounts (Called and displayed as COA)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1034 -msgid "Electronic Trial Balance." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1035 -msgid "DIOT report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1037 -msgid "1. and 2. are considered electronic accounting, and DIOT is a report only available in the context of accounting." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1040 -msgid "You can find all of those reports in :menuselection:`Accounting --> Reporting --> Mexico`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "MX reports" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1049 -msgid "Electronic invoicing has never been so easy, just go to :menuselection:`Accounting -> Reports -> Mexico -> COA` and click the button **Export for SAT (XML)**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "COA for SAT" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1057 -msgid "How to add new accounts ?" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1059 -msgid "If you add an account with the NNN.YY.ZZ encoding convention where NNN.YY is a SAT encoding group, your account will be set up automatically." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1062 -msgid "Example to add an Account for a new Bank account go to :menuselection:`Accounting --> Settings --> Chart of Account` and then create a new account in the «Create» button and try to create an account with the number 102.01.99 once you change to establish the name you will see an automatically configured label, the configured labels are the ones chosen to be used in the COA in XML." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Create account" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1073 -msgid "What is the meaning of the tags?" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1075 -msgid "To know all the possible labels, you can read `Annex 24 `_ on the SAT website in the section called **Código agrupador de cuentas del SAT**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1080 -msgid "When you install the l10n_mx module and your chart of accounts depends on it (this happens automatically when you install the configuration of Mexico as a country in your database), it will have the most common labels by default. If the tag you need is not created, you can create it." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1086 -msgid "Trial Balance" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1088 -msgid "Exactly like the COA but with the credit and debit of the initial balance, once you have correctly configured your COA, you can go to :menuselection:`Reports --> Trial Balance` this is automatically generated and can be exported to XML using the button on the top **Export for SAT (XML)** with the previous selection of the period you want to export." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Electronic verification balance" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1097 -msgid "All normal analysis and listed functions are available here as well as any normal Odoo Report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1100 -msgid "DIOT Report (Requires Accounting App)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1103 -msgid "What is DIOT and the importance of presenting it SAT" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1105 -msgid "When it comes to procedures with the SAT Administration Service, we know that we should not neglect what we present." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1108 -msgid "The DIOT is the Informative Declaration of Operations with Third Parties (DIOT), which is an additional obligation with VAT, where we must give the status of our operations to third parties, or what is considered the same, with our suppliers." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1112 -msgid "This applies to both individuals and Personas Morales, so if we have VAT to present to the SAT and also deal with suppliers it is necessary to send the DIOT." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1116 -msgid "When to file the DIOT and in what format ?" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1118 -msgid "It is easy to present the DIOT, since, like all formats, you can obtain it on the SAT page, it is the electronic form A-29 that you can find on the SAT website." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1121 -msgid "Every month if you have operations with third parties, it is necessary to present the DIOT, as we do with VAT, so if in January we have deals with suppliers, by February we must present the information relevant to said data." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1126 -msgid "Where is DIOT presented?" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1128 -msgid "You can present DIOT in different ways, it is up to you which one you will choose and which one will be more comfortable for you since you will present it every month or every time you have dealings with suppliers." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1132 -msgid "The A-29 form is electronic so you can present it on the SAT page, but this after having made up to 500 registrations." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1135 -msgid "Once these 500 records have been entered in the SAT, you must submit them to the Local Taxpayer Services Administration (ALSC) with correspondence to your tax address, these records can be submitted on a digital storage medium such as a CD or USB, which a Once validated, they will return you, so do not doubt that you will still have these discs and of course, your CD or USB." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1141 -msgid "One more thing to know: batch loading?" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1143 -msgid "When reviewing the official SAT documents in DIOT, you will find the Batch load, and of course the first thing we think is what is that ?, and according to the SAT site it is:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1146 -msgid "The \"batch load\" is the conversion of databases from records of transactions with suppliers made by taxpayers in text files (.txt). These files have the necessary structure for their application and import into the Informative Declaration of Operations with third parties system, avoiding direct capture and consequently, optimizing the time invested in their integration for the presentation in time and form to the SAT." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1152 -msgid "You can use it to present the DIOT, since it is allowed, which will facilitate this operation, so that it does not exist to avoid being in line with the SAT in regards to the Informative Declaration of Operations with Third Parties." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1157 -msgid "`official information `_" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1161 -msgid "How to generate this report in Odoo?" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1163 -msgid "Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third partied (DIOT)`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1022 msgid "DIOT report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1170 -msgid "A report view is displayed, select the last month to report the immediately preceding month or leave the current month if it suits you." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1024 +msgid "The DIOT (Declaración Informativa de Operaciones con Terceros / *Informative Declaration of Operations with Third Parties*) is an additional obligation with the |SAT|, where we give the current status of our creditable and non-creditable payments, withholdings and refunds of VAT from your vendor bills." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "DIOT filter" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1029 +msgid "Unlike other reports, this is uploaded to a software provided by the |SAT| that contains the A-29 form. In Odoo, you can download the records of your transactions in a :file:`.txt` file that you can upload to the form, avoiding direct capture of this data." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1177 -msgid "Click on *Export (XLSX)* or *Print (TXT)*" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1033 +msgid "This file contains the total amount of your payments registered in vendor bills, broken down into the corresponding types of IVA. The :guilabel:`VAT` and :guilabel:`Country` is mandatory for all vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1037 +msgid "To get the report, go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third parties [DIOT]`. Select the month that suits you, and press :guilabel:`DIOT (TXT)` to download the :file:`.txt` file." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Print DIOT" +msgid "DIOT Example." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1183 -msgid "Save the downloaded file in a safe place, go to the SAT website and follow the necessary steps to declare it." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1187 -msgid "Important considerations about your supplier and invoice data for DIOT" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1189 -msgid "All suppliers must have the fields configured in the accounting tab called \"DIOT Information\", the L10N MX Nationality field is completed by simply selecting the appropriate country in the address, not You need to do nothing else there, but the l10n MX type of operation must be configured in all your providers." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1045 +msgid "You need to fill the field :guilabel:`L10N Mx Type of Operation` in the :guilabel:`Accounting` tab of each one of your vendors to prevent validation errors. Make sure that your foreign customers have their country set up for :guilabel:`L10N Mx Nationality` to appear automatically." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "DIOT configuration" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1198 -msgid "There are 3 VAT options for this report, 16%, 0% and exempt, one invoice line in Odoo is considered exempt if there is no tax on it, the other 2 taxes are already configured correctly." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1200 -msgid "Remember that to pay an invoice that represents a prepayment, you must first request the invoice and then pay it and properly reconcile the payment following the standard Odoo procedure." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1202 -msgid "You do not need to fill in all your partner data to try to generate the supplier invoice, you can correct this information when you generate the report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1204 -msgid "Remember that this report only shows vendor invoices that were actually paid." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1206 -msgid "If some of these considerations are not taken into account, a message like this will appear when you generate the DIOT in TXT with all the partners you need to verify this particular report, this is the reason why we recommend to use this report not only for exporting your legal information. obligation, but generate it before the end of the month and use it as your auditory process to see that all your partners are configured correctly." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "DIOT Error" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1217 -msgid "Closing Fiscal Period in Odoo" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1219 -msgid "Before proceeding to the close of the fiscal year, there are some steps that you should normally take to ensure that your accounting is correct, updated and accurate:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1222 -msgid "Make sure that you have fully reconciled your bank account (s) through the end of the year and confirm that the closing book balances match the balances on your bank statements." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1224 -msgid "Verify that all customer invoices have been entered and approved." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1225 -msgid "Confirm that you have entered and approved all vendor bills." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1226 -msgid "Validate all expenses, ensuring their accuracy." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1227 -msgid "Check that all payments received have been entered and recorded exactly." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1232 -msgid "Run a **Tax Report**, and verify that your tax information is correct." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1233 -msgid "Reconcile all accounts on your **Balance Sheet**" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1235 -msgid "Compare your bank balances in Odoo against the current bank balances on your statements. Use the report **Bank Reconciliation** to help you with this." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1237 -msgid "Reconcile all cash and bank account transactions by running your **Old Accounts Receivable** and **Old Accounts Payable** reports" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1239 -msgid "Audit your accounts, making sure you fully understand the transactions that affect them and the nature of the transactions, making sure to include loans and fixed assets." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1242 -msgid "Run the optional function **Payments Matching**, under the *More* drop-down on the Journal options from the Accounting dashboard, validating any Vendor Bill and Customer Invoices with its payments. This step is optional, however it can assist the year-end process if all pending payments and invoices are reconciled, and it can lead to finding errors or mistakes in the system." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1247 -msgid "Your accountant will probably like to check your items in the balance sheet and do some Journal Entries for:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1250 -msgid "Manual year-end adjustments, using the **Journal Audit** report (For example, the **Current Earnings for the Year** and **Retained Earnings reports**)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1252 -msgid "**Work in Progress**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1253 -msgid "**Depreciation Journals**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1254 -msgid "**Loans**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1255 -msgid "**Tax Adjustments**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1257 -msgid "If your accountant is on the year-end audit, they will want to have copies of the balance sheet items (such as loans, bank accounts, prepayments, sales tax reports, etc ...) to compare against. your balances in Odoo." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1261 -msgid "During this process, it is a good practice setting the **Closing Date for Non-Advisers** to the last day of the preceding financial year, which is set under the accounting settings. In this way, the accountant can trust that no one else is changing the previous year's transactions while auditing the books." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Fiscal year" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1271 -msgid "Accounting Closing Process" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1273 -msgid "In Odoo there is no need to make a specific year-end entry to close the reporting income accounts . The result of the exercise is automatically calculated in the account type (Current Year Earnings) and the difference between Income - Expenses will be accumulated to calculate it." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1277 -msgid "The reports are created in real-time, which means that the **Income Report** corresponds directly to the closing date of the year that you specify in Odoo. In addition, at any time that you generate the **Income Report**, the start date will correspond to the start date of the **Fiscal Year** and the account balances will all be 0." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1282 -msgid "As of December 31, the Balance Sheet shows the earnings of the Current Year that do not have been recognized (Account type Total Current Year Unallocated Earnings in MX account 305.01.01 ['current year earnings' type])" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Balance sheet closing" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1290 -msgid "The accountant should create a Journal Entry to recognize the result of the year in Accumulated Earnings from previous years on the account \"previous years results\" account (304.01.01 in Mexico) - that is an equity account." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1294 -msgid "After posting the Journal Entry, click on *Mark as Closing Entry for the Fiscal Year*. This step is important because it is linked to the Trial Balance report. If this Journal Entry is not marked as a Closing Entry, the Trial Balance won't be correct." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1298 -msgid "The simplified accounting entry would look like this:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Closing journal entry" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1304 -msgid "Once the accountant has created the journal entry to locate the **Current Earnings for the Year**, they must set the **Closing Date** to the last day of the fiscal year. Making sure that before doing this, whether or not the current gain of the year in the **Balance Sheet** is properly reporting a balance 0." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Check BS closing" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1314 -msgid "Extra Recommended features" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1317 -msgid "Contacts App (Free)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1319 -msgid "If you want to properly manage your customers, suppliers and addresses, this module, even if it is not a technical need, it is highly recommended to install it." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1323 -msgid "Multi-currency (Requires Accounting application)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1325 -msgid "In Mexico, almost all companies send and receive payments in different currencies. If you want to do this you can enable the use of multi-currency. You should also enable synchronization with the **Mexican Bank Service**, as this would allow you to automatically have the exchange rate from the SAT without having to manually create this information every day in Odoo." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1330 -msgid "Go to settings and enable the multi-currency feature." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Multi currency configuration" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1337 -msgid "Enabling Explicit errors on the CFDI using the XSD local validator (CFDI 3.3)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1339 -msgid "Frequently you want receive explicit errors from the fields incorrectly set on the xml, those errors are better informed to the user if the check is enable, to enable the Check with xsd feature follow the next steps (with the :ref:`developer mode ` enabled)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1344 -msgid "Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1345 -msgid "Look for the Action called \"Download XSD files to CFDI\"" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1346 -msgid "Click on button \"Create Contextual Action\"" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1347 -msgid "Go to the company form :menuselection:`Settings --> Users&Companies --> Companies`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1348 -msgid "Open any company you have." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1349 -msgid "Click on \"Action\" and then on \"Download XSD file to CFDI\"." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Download XSD files to CFDI from the Companies list view on Odoo" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1355 -msgid "Now you can make an invoice with any error (for example a product without code which is pretty common) and an explicit error will be shown instead a generic one with no explanation." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1360 -msgid "If you see an error like this:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "``The cfdi generated is not valid``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "``attribute decl. 'TipoRelacion', attribute 'type': The QName value '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_TipoRelacion' does not resolve to a(n) simple type definition., line 36``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1367 -msgid "This can be caused by a database backup restored in another server, or when the XSD files are not correctly downloaded. Follow the same steps as above but:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1371 -msgid "Go to the company in which the error occurs." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1372 -msgid "Click on *Action* and then on *Download XSD file to CFDI*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1375 -msgid "Common problems and errors" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1377 -msgid "**Error messages** (Only applicable on CFDI 3.3):" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1379 -msgid "``9:0:ERROR:SCHEMASV:SCHEMAV_CVC_MINLENGTH_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'minLength'] The value '' has a length of '0'; this underruns the allowed minimum length of '1'.``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1384 -msgid "``9:0:ERROR:SCHEMASV:SCHEMAV_CVC_PATTERN_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'pattern'] The value '' is not accepted by the pattern '[^|]{1,100}'.``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1388 -msgid "**Solution**: You forgot to set the proper \"Reference\" field in the product, please go to the product form and set your internal reference properly." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1392 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1433 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1464 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1485 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1493 -msgid "**Error messages**:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1394 -msgid "``6:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}RegimenFiscal': The attribute 'Regimen' is required but missing.``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1397 -msgid "``5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'RegimenFiscal' is required but missing.``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1400 -msgid "**Solution**: You forgot to set the proper \"Fiscal Position\" on the partner of the company. Go to customers, remove the customer filter and look for the partner called as your company and set the proper fiscal position which is the kind of business your company does related to SAT list of possible values, another option can be that you forgot to follow the considerations about fiscal positions." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1407 -msgid "You need to go to Fiscal Position settings and set the proper code (it is the first 3 numbers of the name), for example, for the test, you need to set 601, it will look like the picture." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "Fiscal position error" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1415 -msgid "For testing purposes this value must be set to ``601 - General de Ley Personas Morales`` which is the one required for the VAT demo." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1418 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1450 -msgid "**Error message**:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1420 -msgid "``2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'FormaPago': [facet 'enumeration'] The value '' is not an element of the set {'01', '02', '03', '04', '05', '06', '08', '12', '13', '14', '15', '17', '23', '24', '25', '26', '27', '28', '29', '30', '99'}``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1426 -msgid "**Solution**: The payment method is required on your invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Payment method error" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1435 -msgid "``2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': [facet 'enumeration'] The value '' is not an element of the set {'00``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1438 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1452 -msgid "``2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' is not a valid value of the atomic type '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'.``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1441 -msgid "``5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'Rfc' is required but missing.``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1444 -msgid "**Solution**: You must configure your company address correctly, this is a mandatory group of fields, you can go to your company configuration in :menuselection:`Settings --> Users & Companies --> Companies` and fill complete all the mandatory fields for your address by following the steps in this section: :ref:`mx-legal-info`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1457 -msgid "**Solution**: The postal code of your company address is not valid for Mexico, please correct it." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "ZIP code error" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1466 -msgid "``18:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing.``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1469 -msgid "``34:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing.\", '')``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1473 -msgid "**Solution**: Set the Mexican name for the 0% and 16% tax in your system and use it on the invoice. Your tax, which represents 16% VAT and 0%, must have the **Factor Type** field set to *Tasa*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "Factor type error" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "Rate error" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "``CCE159``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "``The XXXX attribute must be registered if the key of cce11: ComercioExterior: TipoOperacion registered is '1' or '2'.``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1491 -msgid "**Solution**: It is necessary to specify the Incoterm." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "``CCE209``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 -msgid "``The attribute cce11: Foreign Trade: Goods: Goods: Customs Unit must have the value specified in the catalog catCFDI: c_FraccionArancelaria column 'UMT' when the attribute cce11: Foreign Trade: Goods: Me``" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1500 -msgid "**Solution**: The Tariff Fraction must have the code of the unit of measure 01, corresponding to Kilograms." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1504 -msgid "Glossary" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1506 -msgid ":abbr:`CFDI (Comprobante Fiscal Digital por Internet)`: Online Digital Tax Receipt" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1507 -msgid ":abbr:`CSD (Certificado de Sello Digital)`: Digital Seal Certificate" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1508 -msgid ":abbr:`PAC (Proveedores Autorizados de Certificación)`: Authorized Certification Provider" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1509 -msgid "Stamp: Digital signature of the electronic invoice" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1510 -msgid "Addenda: Complement of information that can be attached to an Internet Digital Tax Receipt (CFDI) normally required by certain companies in Mexico such as Walmart, Tiendas Sorianas, etc." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1512 -msgid ":abbr:`UUID (Universally Unique Identifier)`: It is the acronym in English of the Universally Unique Identifier. The UUID is the equivalent of Folio Fiscal, it is composed of 32 hexadecimal digits, shown in 5 groups separated by hyphens." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1515 -msgid "LCO: List of Obliged Taxpayers (LCO) is a list issued by the SAT that accounts for all the taxpayers whom it authorizes the issuance of invoices and payroll receipts. This means that, to be able to electronically bill your clients, you must be in this database." +msgid "DIOT Example contact." msgstr "" #: ../../content/applications/finance/fiscal_localizations/netherlands.rst:3 @@ -19340,10 +18968,6 @@ msgstr "" msgid "On Odoo, go to :menuselection:`Accounting --> Configuration --> Settings`. Under :guilabel:`ZATCA API Integration`, select the :guilabel:`Simulation (Pre-Production)` :guilabel:`API mode` and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:91 -msgid "Sales journals" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:93 msgid "Each sales journal on Odoo needs to be configured. To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open any sales journal (e.g., Customer Invoices), and go to the :guilabel:`ZATCA` tab. Once there, enter any :guilabel:`Serial Number` to identify the journal." msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index f4c822dc7..90a898464 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-11 16:10+0000\n" +"POT-Creation-Date: 2023-10-09 08:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1572,331 +1572,619 @@ msgid "This value can be changed in :ref:`developer mode `. Go t msgstr "" #: ../../content/applications/general/email_communication/email_template.rst:3 -msgid "Email Templates" +msgid "Email templates" msgstr "" #: ../../content/applications/general/email_communication/email_template.rst:5 -msgid "We all know writing good emails is vital to get a high response rate, but you do not want to rewrite the same structure every time, do you? That is where email templates come in. Without the need to rewrite the entire email structure every time, you save time to focus on the content. Multiple templates also let you deliver the right message to the right audience, improving their overall experience with the company." +msgid "Email templates are saved emails that are used repeatedly to send emails from the database. They allow users to send quality communications, without having to compose the same text repeatedly." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:12 -msgid "The email templates use QWeb. The composer allows you to edit emails in their final rendering, making customizations more robust as you don’t have to edit code." +#: ../../content/applications/general/email_communication/email_template.rst:8 +msgid "Creating different templates that are tailored to specific situations lets users choose the right message for the right audience. This increases the quality of the message and the overall engagement rate with the customer." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:16 -msgid "Defining a default reply to on your mail template" +#: ../../content/applications/general/email_communication/email_template.rst:13 +msgid "Email templates in Odoo use QWeb or XML, which allows for editing emails in their final rendering, making customizations more robust, without having to edit any code whatsoever. This means that Odoo can use a Graphical User Interface (GUI) to edit emails, which edits the backend code. When the received email is read by the end user's program different formatting and graphics will appear in the final form of it." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:18 -msgid "Although the field *reply to* is available within the mail templates, **this field is only used for mass mailing** mode (this means when sending templates on what we call bulk emailing). You can send emails in bulk in almost every app that has a list view. Select the records you want and click on the action button. If you have an option to send an email, you will see a mail composer with possible values to define:" +#: ../../content/applications/general/email_communication/email_template.rst:19 +msgid "Access email templates in :ref:`developer mode ` by navigating to :menuselection:`Settings app --> Technical menu --> Email --> Email Templates`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:23 +msgid "Editing email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:25 +msgid "The *powerbox* feature can be used when working with email templates. This feature provides the ability to directly edit the formatting and text in an email template, as well as the ability to add links, buttons, appointment options, or images." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:29 +msgid "Additionally, the XML/HTML code of the email template can be edited directly, via the :guilabel:`` icon." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:32 +msgid "*Dynamic placeholders* (text that references fields within Odoo to auto-fill information on the template) are available for the :guilabel:`Email Configuration` fields, the :guilabel:`Subject`, and the :guilabel:`Language`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:37 +msgid "Powerbox" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:39 +msgid "The *powerbox* feature is an enriched text editor with various formatting, layout, and text options. It can also be used to add XML/HTML features in an email template. The powerbox feature is activated by typing a forward slash `/` in the body of the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:43 +msgid "When a forward slash `/` is typed in the body of an email template, a drop-down menu appears with the following options:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:46 +msgid ":guilabel:`Basic Blocks`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:48 +msgid ":guilabel:`Heading 1`: Big section heading." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:49 +msgid ":guilabel:`Heading 2`: Medium section heading." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:50 +msgid ":guilabel:`Heading 3`: Small section heading." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:51 +msgid ":guilabel:`Text`: Paragraph block." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:52 +msgid ":guilabel:`Bulleted list`: Create a simple bulleted list." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:53 +msgid ":guilabel:`Numbered list`: Create a list with numbering." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:54 +msgid ":guilabel:`Checklist`: Track tasks with a checklist." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:55 +msgid ":guilabel:`Table`: Insert a table." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:56 +msgid ":guilabel:`Switch direction`: Switch the text's direction." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:57 +msgid ":guilabel:`Separator`: Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:58 +msgid ":guilabel:`Quote`: Add a blockquote section." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:59 +msgid ":guilabel:`Code`: Add a code section." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:60 +msgid ":guilabel:`Appointment`: Add a specific appointment." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:61 +msgid ":guilabel:`Calendar`: Schedule an appointment." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:63 +msgid ":guilabel:`Navigation`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:65 +msgid ":guilabel:`Link`: Add a link." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:66 +msgid ":guilabel:`Button`: Add a button." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:68 +msgid ":guilabel:`Medias`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:70 +msgid ":guilabel:`Image`: Insert an image." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:73 +msgid "To use any of these options, click on the desired feature from the powerbox drop-down menu. To format existing text with a text-related option (e.g. :guilabel:`Heading 1`, :guilabel:`Switch direction`, etc.), highlight the text, then type in the activator key (forward slash) `/`, and select the desired option from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:0 +msgid "Powerbox feature in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:83 +msgid "XML/HTML code editor" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:85 +msgid "To access the XML/HTML editor for an email template, first enter :ref:`developer mode `. Then, click the :guilabel:`` icon in the upper-right corner of the template, and proceed to edit the XML/HTML. To return to the standard text editor, click the :guilabel:`` icon again." msgstr "" #: ../../content/applications/general/email_communication/email_template.rst:-1 -msgid "Composer in mass mailing mode after selecting multiple quotations." +msgid "HTML editor in the email template." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:28 -msgid "You can also define them by default on the template:" +#: ../../content/applications/general/email_communication/email_template.rst:95 +msgid "The XML/HTML editor should be accessed with caution as this is the backend code of the template. Editing the code can cause the email template to break immediately or when upgrading the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:100 +msgid "Dynamic placeholders" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:102 +msgid "*Dynamic placeholders* reference certain fields within the Odoo database to produce unique data in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:106 +msgid "Many companies like to customize their emails with a personalized piece of customer information to grab attention. This can be accomplished in Odoo by referencing a field within a model by inserting a dynamic placeholder. For example, a customer's name can be referenced in the email from the :guilabel:`Customer` field on the :guilabel:`Sales Order` model. The dynamic placeholder for this field is: `{{ object.partner_id }}`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:112 +msgid "Dynamic placeholders are encoded to display fields from within the database. Dynamic placeholders can **only** be used in the fields present in the :guilabel:`Email Configuration` tab, the :guilabel:`Subject` of the email, and the :guilabel:`Language`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:116 +msgid "Dynamic placeholders can be used with the following fields on an email template:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:118 +msgid ":guilabel:`Subject` (:guilabel:`Content` tab)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:119 +msgid ":guilabel:`From` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:120 +msgid ":guilabel:`To (Emails)` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:121 +msgid ":guilabel:`To (Partners)` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:122 +msgid ":guilabel:`CC` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:123 +msgid ":guilabel:`Reply-To` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:124 +msgid ":guilabel:`Language` (:guilabel:`Advanced Settings` tab)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:126 +msgid "The :guilabel:`Dynamic Placeholder Generator`, which is the last tab on the email template, creates placeholders for the aforementioned fields. Dynamic placeholders may also be inserted in the HTML code, but this task is out of the scope of Odoo Support." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:130 +msgid "To use the *Dynamic Placeholder Generator*, navigate to the :guilabel:`Dynamic Placeholder Generator` tab. Select the field that the dynamic placeholder should reference using the :guilabel:`Field` drop-down menu. Should a :guilabel:`Sub-Model` or :guilabel:`Sub-Field` need to be specified, set those by selecting the corresponding drop-down menu. These fields should be set automatically after setting the :guilabel:`Field`, although in some instances these fields will remain empty. The dynamic placeholder will appear in the :guilabel:`Placeholder Expression` field. Copy and paste the placeholder expression into the appropriate field in the tabs of the email template, as listed in the bulleted list above." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:140 +msgid "Each unique combination of :guilabel:`Fields`, :guilabel:`Sub-models` and :guilabel:`Sub-fields` creates a different dynamic placeholder. Imagine it as a combination to the field that is being created." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:144 +msgid "To search the available fields, simply click the drop-down menu next to :guilabel:`Field` and select one, or click :guilabel:`Search More` to select from all of the available fields for the model that the email template is created for." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:149 +msgid ":doc:`../../productivity/studio/models_modules_apps`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:152 +msgid "These fields can also be accessed in :ref:`developer mode `. On a contact form (or other relevant form in Odoo), navigate to the information that should be referenced in the dynamic placeholder, and hover over the field name. A box of backend information will reveal itself with the specific Odoo :guilabel:`Field` name in the backend. Search for this field in the :guilabel:`Field` drop-down menu in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:0 +msgid "Backend information box of fields on a model." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:163 +msgid ":ref:`Views and fields in the developer documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:166 +msgid "Customizing email templates are out of the scope of Odoo Support." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:169 +msgid "Default reply on email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:171 +msgid "Under the :guilabel:`Email Configuration` tab on an email template, there is a :guilabel:`Reply To` field. In this field, add email addresses to which replies are redirected when sending emails en masse using this template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:176 +msgid "A Add multiple email addresses by adding a comma `,` between the addresses or dynamic placeholders." msgstr "" #: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "Reply-to field on template." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:34 -msgid "Because of this, setting a value in this field is useless as the value defined will be totally ignored. The default *reply-to* value is the default catchall email address to ensure a communication between your customer and your Odoo database. For more information about the way the catchall works, please check :ref:`how to manage inbound messages `." +#: ../../content/applications/general/email_communication/email_template.rst:183 +msgid "The :guilabel:`Reply To` field is **only** used for mass mailing (sending emails in bulk). Bulk emails can be sent in almost every Odoo application that has a list view option." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:40 -msgid "Transactional emails and corresponding URL for each company" +#: ../../content/applications/general/email_communication/email_template.rst:186 +msgid "To send mass mails, while in :guilabel:`list` view, check the boxes next to the desired records where the emails are to be sent, click the :guilabel:`Action` button (represented by a :guilabel:`⚙️ (gear)` icon), and select the desired email option from the :guilabel:`Action` drop-down menu. Email options can vary by the particular list view and application." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:42 -msgid "When using Odoo, multiple events trigger the sending of automated emails. These emails are known as transactional emails and sometimes contain links pointing to your Odoo database." +#: ../../content/applications/general/email_communication/email_template.rst:191 +msgid "If it is possible to send an email, a mail composer pop-up window appears, with values that can be defined and customized. This option will be available on the :guilabel:`Action` button on pages where emails can be sent in bulk---for example, on the :guilabel:`Customers` page of the CRM app. This action occurs throughout the Odoo database." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:45 -msgid "By default, links generated by the database use the dynamic web.base.url key defined in the system parameters. More information about this :ref:`parameter `." +#: ../../content/applications/general/email_communication/email_template.rst:-1 +msgid "Email composer in mass mailing mode with reply-to highlighted." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:48 -msgid "If the website application isn't installed, the web.base.url key will always be the default parameter used to generate all the links." +#: ../../content/applications/general/email_communication/email_template.rst:201 +msgid "Transactional emails and corresponding URLs" msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:51 -msgid "It’s important to know that this key can only have a single value, meaning that in a multi-website/company database environment, even if you have a specific domain name for each website, the links generated to share a document or within a transactional email might remain the same, whatever the website/company related to the sending of the email/document." +#: ../../content/applications/general/email_communication/email_template.rst:203 +msgid "In Odoo, multiple events can trigger the sending of automated emails. These emails are known as *transactional emails*, and sometimes contain links redirecting to the Odoo database." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:56 -msgid "This is not always the case as some Odoo applications have a link established in the database with the website application, meaning that in this case, if a specific domain is defined for the websites, the URL generated in the email template will use the domain defined on the corresponding website of the company." +#: ../../content/applications/general/email_communication/email_template.rst:206 +msgid "By default, links generated by the database use the dynamic `web.base.url` key defined in the system parameters. For more information about this, see :ref:`system parameters `." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:62 -msgid "A document shared using the documents application will always use the web.base.url key, as the document shared isn't associated with any particular website. Meaning that the URL will always be the same (the web.base.url key value), whatever the company it's shared from, this is a known limitation!" +#: ../../content/applications/general/email_communication/email_template.rst:210 +msgid "If the *Website* application is not installed, the `web.base.url` key will always be the default parameter used to generate all the links." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:67 -msgid "On the other hand, sales orders made by a customer on one of your Odoo e-commerce websites have a link established with the website from which the order was made. As a result, the e-mail sent for the sales orders uses the domain name defined for the corresponding website to generate the links." +#: ../../content/applications/general/email_communication/email_template.rst:214 +msgid "The `web.base.url` key can only have a single value, meaning that, in a multi-website or multi-company database environment, even if there is a specific domain name for each website, the links generated to share a document (or the links within a transactional email) may remain the same, regardless of which website/company is related to the sending of the email/document." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:71 -msgid "For more information about how to configure your domains, we invite you to check :doc:`our domain name documentation `." +#: ../../content/applications/general/email_communication/email_template.rst:220 +msgid "If the :guilabel:`Value` of the :guilabel:`web.base.url` system parameter is equal to `https://www.mycompany.com` and there are two separate companies in Odoo with different website URLs: `https://www.mycompany2.com` and `https://www.mycompany1.com`, the links created by Odoo to share a document, or send a transactional email, come from the domain: `https://www.mycompany.com`, regardless of which company sends the document or email." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:75 +#: ../../content/applications/general/email_communication/email_template.rst:226 +msgid "This is not always the case, as some Odoo applications (*eCommerce*, for example) have a link established in the database with the *Website* application. In that case, if a specific domain is defined for the website, the URL generated in the email template uses the domain defined on the corresponding website of the company." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:232 +msgid "When a customer makes a purchase on an Odoo *eCommerce* website, the order has an established link with that website. As a result, the links in the confirmation email sent to the customer use the domain name for that specific website." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:237 +msgid "A document shared using the *Documents* application will **always** use the `web.base.url` key, as the document shared is not associated with any particular website. This means that the URL will always be the same (the `web.base.url` key value), no matter what company it's shared from. This is a known limitation." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:242 +msgid "For more information about how to configure domains, check out the :doc:`domain name documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:246 msgid "Updating translations within email templates" msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:77 -msgid "Email templates are automatically translated. Changing the translations shouldn’t be necessary. However, if for a specific reason you’d like to change some of the translations, this can be done." +#: ../../content/applications/general/email_communication/email_template.rst:248 +msgid "In Odoo, email templates are automatically translated for all users in the database for all of the languages installed. Changing the translations shouldn't be necessary. However, if for a specific reason, some of the translations need to be changed, it can be done." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:80 -msgid "Like any modification in the code, keep in mind that modifications that aren’t done correctly (for example modifications leading to bad syntax) can break the template, as a result, the template will appear blank." +#: ../../content/applications/general/email_communication/email_template.rst:253 +msgid "Like any modification in the code, if translation changes are not done correctly (for example, modifications leading to bad syntax), it can break the template, and as a result, the template will appear blank." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:84 -msgid "In order to edit your translations, follow these steps from the template." +#: ../../content/applications/general/email_communication/email_template.rst:257 +msgid "In order to edit translations, first enter :ref:`developer mode `. Then, on the email template, click on the :guilabel:`Edit` button, and then click on the language button, represented by the initials of the language currently being used (e.g. :guilabel:`EN` for English)." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:86 -msgid "Click on the edit button, then on the language button" +#: ../../content/applications/general/email_communication/email_template.rst:-1 +msgid "Edit the language of a template." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:0 -msgid "Edit the language of a template" +#: ../../content/applications/general/email_communication/email_template.rst:266 +msgid "If there aren't multiple languages installed and activated in the database, or if the user does not have administration access rights, the language button will not appear." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:92 -msgid "A pop-up window with the different languages installed on the database will be displayed. From here, editing the translations will be possible. Don't forget to hit the save button to preserve your changes." +#: ../../content/applications/general/email_communication/email_template.rst:269 +msgid "A pop-up window with the different languages installed on the database appears. From this pop-up, editing of translations is possible. When the desired changes have been made, click the :guilabel:`Save` button to save the changes." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:0 -msgid "Translation of the body of the Application template in the different languages installed." +#: ../../content/applications/general/email_communication/email_template.rst:-1 +msgid "Translation of the body of the Appointment Booked template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:278 +msgid "When editing the translations, the default language set in the database appears in **bold**." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:3 -msgid "FAQ" +msgid "Email issues" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:5 -msgid "This document contains an explanation of the most recurring mailing concerns." +msgid "This document contains an explanation of the most recurring emailing issues in Odoo." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:7 -msgid "We will start by addressing issues of outgoing emails (ex: my client has not received my email), and then, of incoming emails (ex: I do not receive responses from my customers in the database)." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:11 +#: ../../content/applications/general/email_communication/faq.rst:8 msgid "Outgoing emails" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:16 -msgid "What do you have to check if your email is not sent?" +#: ../../content/applications/general/email_communication/faq.rst:13 +msgid "Email is not sent" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:18 -msgid "The first indicator showing you that the email has not been sent is the red envelope next to the date and time of the message." +#: ../../content/applications/general/email_communication/faq.rst:15 +msgid "The first indicator showing that an email has not been sent is the presence of a red :guilabel:`✉️ (envelope)` icon, next to the date and time of the message, located in the chatter." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:-1 -msgid "Red envelope displayed in chatter" +msgid "Red envelope icon displayed in chatter." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:26 +#: ../../content/applications/general/email_communication/faq.rst:22 +msgid "Unsent emails also appear in the Odoo email queue. In :ref:`developer mode `, the email queue can be accessed by going to :menuselection:`Settings app --> Technical menu --> Email --> Emails`. Unsent emails appear in turquoise, while sent emails appear in grey." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:27 msgid "Common error messages" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:31 -msgid "You reached your daily limit:" +#: ../../content/applications/general/email_communication/faq.rst:32 +msgid "Daily limit reached" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:-1 -msgid "Warning in Odoo upon email limit reached" +msgid "Warning in Odoo upon email limit reached." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:37 -msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, and sometimes even per minute. This is the same for Odoo, we have to limit our customers to prevent our e-mail servers from being blacklisted." +#: ../../content/applications/general/email_communication/faq.rst:38 +msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, or sometimes, per minute. This is the same for Odoo, which limits a customer's sending to prevent Odoo's email servers from being blacklisted." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:41 +#: ../../content/applications/general/email_communication/faq.rst:42 msgid "Here are the default limits for new databases:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:43 -msgid "200 emails/day for Odoo Online and Odoo.sh databases with an active subscription," -msgstr "" - #: ../../content/applications/general/email_communication/faq.rst:44 -msgid "20 emails/day for one-app free databases," +msgid "**200 emails per day** for Odoo Online and Odoo.sh databases with an active subscription." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:45 -msgid "50 emails/day for trial databases," +msgid "**20 emails per day** for one-app free databases." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:46 -msgid "in case of migration, your daily limit might be reset to 50 emails a day." +msgid "**50 emails per day** for trial databases." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:48 -msgid "In case you hit the limit, you can:" +#: ../../content/applications/general/email_communication/faq.rst:47 +msgid "In the case of migration, the daily limit might be reset to 50 emails per day." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:50 -msgid "Ask our support team to increase your daily limit. We will analyze the situation of your database depending on (non-exhaustive list):" +#: ../../content/applications/general/email_communication/faq.rst:49 +msgid "If the daily limit is reached:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:53 -msgid "How many users in your database," +#: ../../content/applications/general/email_communication/faq.rst:51 +msgid "Contact the Odoo support team, who may increase the daily limit depending on the following factors:" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:54 -msgid "Which apps are installed," +msgid "How many users are in the database?" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:55 -msgid "Your bounce rate: the percentage of email addresses that did not receive your emails because it was returned by a mail server on its way to the final recipient. You can contact the `support `_." +msgid "Which apps are installed?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:56 +msgid "The bounce rate: the percentage of email addresses that did not receive emails because they were returned by a mail server on its way to the final recipient." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:59 -msgid "Use your own outgoing email server to be independent of Odoo’s mail limit (please refer to :doc:`the corresponding documentation `)," +msgid "Use an external outgoing email server to be independent of Odoo's mail limit (refer to the corresponding :doc:`email documentation `)." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:61 -msgid "Wait until 11pm UTC for the reset and click on the retry button: The :ref:`Developer mode ` must be activated. Then, go to :menuselection:`Settings --> Technical --> Emails`" +#: ../../content/applications/general/email_communication/faq.rst:62 +msgid "Wait until 11 PM (UTC) for the daily limit to reset, and retry sending the email. In :ref:`developer mode `, go to :menuselection:`Settings app --> Technical menu --> Email --> Emails`, then click the :guilabel:`Retry` button next to an unsent email." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:-1 -msgid "Retry button of an emails" +#: ../../content/applications/general/email_communication/faq.rst:67 +msgid "The daily email limit is comprehensive to the database. By default, any internal message, notification, logged note, etc. counts as an email in the daily limit if it notifies someone via email. This can be mitigated by receiving :ref:`notifications in Odoo `, instead of emails." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:69 -msgid "The daily limit is global to your database and can rise quickly! By default an internal message, a notification, a note, etc. counts as an email in your daily limit if it notifies someone." +#: ../../content/applications/general/email_communication/faq.rst:73 +msgid "SMTP error" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:72 -msgid "You can mitigate this by receiving your :ref:`notifications in Odoo ` instead of by emails." +#: ../../content/applications/general/email_communication/faq.rst:75 +msgid "Simple Mail Transport Protocol (SMTP) error messages explain why an email wasn't transmitted successfully. :abbr:`SMTP (Simple Mail Transport Protocol)` is a protocol to describe the email structure, and transmits data from messages over the Internet. The error messages generated by email services are helpful tools to diagnose and troubleshoot email problems." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:76 -msgid "SMTP Error" +#: ../../content/applications/general/email_communication/faq.rst:81 +msgid "This is an example of a 554 SMTP permanent delivery error: `554: delivery error: Sorry, your message to ------@yahoo.com cannot be delivered. This mailbox is disabled (554.30). - mta4471.mail.bf1.yahoo.com --- Below this line is a copy of the message.`" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:78 -msgid "You can find out why an email wasn't transmitted successfully by reviewing the Simple Mail Transport Protocol (SMTP) error messages. SMTP is a protocol to describe the email structure and transmit it over the Internet, and the error messages generated by email services are helpful tools to diagnose and troubleshoot email problems." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:84 -msgid "No Error" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:86 -msgid "Odoo is not always capable of providing information for the reason it failed. The different providers implement a personalized policy of the bounce emails and it is not always possible for Odoo to interpret it correctly." +#: ../../content/applications/general/email_communication/faq.rst:85 +msgid "The debug menu can be used to investigate SMTP sending issues from a database. To access the menu, :ref:`developer mode ` must be activated. Once activated, navigate to the :menuselection:`Debug Menu` in the top right of the menu bar (the :guilabel:`🐞 (bug)` icon), :menuselection:`Debug Menu --> Manage Messages`" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:90 -msgid "If you have this problem on a recurring basis with the same client or the same domain, please do not hesitate to contact `Odoo Support `_ for help in finding a reason." +msgid "The :guilabel:`Manage Messages` menu opens a list of all the messages sent in a particular record. Within each message there is information on sending, including the type, and subtype, of the message." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:93 -msgid "Note: in such case, one of the most common reasons is related to :ref:`SPF ` and/or :ref:`DKIM ` configuration." +#: ../../content/applications/general/email_communication/faq.rst:94 +msgid "Other information includes to whom the message was sent, and whether Odoo received a bounce-back message from an email server." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:97 -msgid "Why is my email sent late?" +#: ../../content/applications/general/email_communication/faq.rst:-1 +msgid "Manage messages menu option on the debug menu." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:99 -msgid "It may happen that you schedule an email campaign but it is not sent on time. We know that we use a delayed job to send emails that we consider as not urgent (Newsletters concept such as mass mailing, marketing automation, events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. We use that policy in order to avoid cluttering the mail servers and prioritize the communication." +#: ../../content/applications/general/email_communication/faq.rst:102 +msgid "A user must be on a view in Odoo that has a chatter in order for the :guilabel:`Manage Messages` menu option to appear." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:105 -msgid "The emails considered urgent (communication from one person to another one such as Sales Orders, Invoices, Purchase Orders, etc.) are sent directly." +#: ../../content/applications/general/email_communication/faq.rst:106 +msgid "No error populated" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:108 +msgid "Odoo is not always capable of providing information for the reason it failed. The different email providers implement a personalized policy of bounced emails, and it is not always possible for Odoo to interpret it correctly." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:112 +msgid "If this is a recurring problem with the same client, or the same domain, do not hesitate to contact `Odoo Support `_ for help in finding a reason." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:116 +msgid "One of the most common reasons for an email failing to send with no error message is related to :ref:`SPF ` and/or :ref:`DKIM ` configuration. Also, check to make sure the `mail.bounce.alias` is defined in the *system parameters*. Access system parameters in :ref:`developer mode ` by navigating to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:124 +msgid "Email is sent late" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:126 +msgid "Email campaigns send at a scheduled time, using a delay pre-programed in the database. Odoo uses a delayed task to send emails that are considered \"not urgent\" (newsletter formats, such as: mass mailing, marketing automation, and events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. Odoo uses that policy in order to avoid cluttering the mail servers and, instead, prioritizes individual communication. This **cron** is called :guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode ` by going to :menuselection:`Settings app --> Technical menu --> Automation --> Scheduled Actions`." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:-1 msgid "Email scheduled to be sent later." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:112 -msgid "By default, the Mass Mailing cron runs every 60 minutes. So, you should wait maximum an hour before the campaign is actually sent." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:116 -msgid "Incoming emails" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:118 -msgid "When you have an issue with incoming emails, there might not be an indication per se in Odoo. This is the client who tries to contact a database who will get a bounce (most of the time 550: mailbox unavailable)." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:123 -msgid "Emails are not received" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:125 -msgid "Depending on the platform you are using:" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:127 -msgid "The **Odoo.sh** users can find their live logs on the folder :file:`~/logs/`." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:129 -msgid "The folder :file:`~/logs/` (preferably accessed by the command line) of an Odoo.sh contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM UTC. The two last days are not compressed, while the older ones are, in order to gain space. The naming of the files for Today and Yesterday are :file:`odoo.log` and :file:`odoo.log.1`. For the following, they are named with their dates and compressed. See the Odoo.sh documentation about :ref:`logs `. Use the command ``grep`` and ``zgrep`` (for the compressed ones) to search through the files." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:137 -msgid "**Odoo Online** users won’t have access to their logs. However you can still contact `Odoo Support `_ , if you have a recurring issue with the same client or domain." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:142 -msgid "Get help from support" +#: ../../content/applications/general/email_communication/faq.rst:140 +msgid "What is a **cron**? A cron is an action that Odoo runs in the background to execute particular code to complete a task." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:144 -msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful:" +msgid "By default, the *Mass Mailing cron* runs every 60 minutes. This can be changed to no less than 5 minutes. However, running the action every 5 minutes would bog down the Odoo database (stress the system), so this is not recommended. To edit the mass mailing cron, select the scheduled action :guilabel:`Mail: Email Queue Manager`, and proceed to make any necessary adjustments." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:147 -msgid "The **EML** of the email, stating for *Electronic Mail*, is the file format containing all the technical information required for an investigation. The documentation of your own email provider might help you on how to get your EML files. Once you get the EML of the email, adding it in the attachment of your ticket is the most efficient way for us to investigate. The support will mainly focus on redundant issues." +#: ../../content/applications/general/email_communication/faq.rst:149 +msgid "Emails that are considered urgent (communication from one person to another, such as sales orders, invoices, purchase orders, etc.) are sent immediately." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:154 -msgid "`Gmail documentation `_" +#: ../../content/applications/general/email_communication/faq.rst:153 +msgid "Incoming emails" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:156 -msgid "`Outlook documentation `_" +#: ../../content/applications/general/email_communication/faq.rst:155 +msgid "When there is an issue with incoming emails, there might not be an indication, per se, in Odoo. It is the sending email client, who tries to contact a database, that will get a bounce-back message (most of the time a :guilabel:`550: mailbox unavailable` error message)." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:159 -msgid "The exact flow you are following in order to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:" +#: ../../content/applications/general/email_communication/faq.rst:160 +msgid "Email is not received" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:162 -msgid "Is this simply a reply from an email going out from Odoo ?" +msgid "The steps that should be taken depend on the Odoo platform where the database is hosted." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:164 -msgid "Are you using an incoming email server or somehow redirecting?" +msgid "**Odoo.sh** users can find their live logs on the folder :file:`~/logs/`." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:166 -msgid "Can you provide us with an example of an email that has been correctly forwarded ?" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:168 -msgid "Providing answers to the following questions:" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:170 -msgid "Is it a generic issue or is it specific to a use case? If yes, which one exactly?" +msgid "Logs are a stored collection of all the tasks completed in a database. They are a text-only representation, complete with timestamps of every action taken on the Odoo database. This can be helpful to track emails leaving the database. Failure to send can also be seen by logs that indicate that the message tried to send repeatedly. Logs will show every action to the email servers from the database." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:172 -msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database and display the :ref:`red envelope `." +msgid "The folder :file:`~/logs/` (accessed by the command line or on the Odoo.sh dashboard) of an Odoo.sh database contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM (UTC)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:177 +msgid "The two most recent days (today and yesterday) are not compressed, while the older ones are, in order to save space. The naming of the files for today and yesterday are respectively: :file:`odoo.log` and :file:`odoo.log.1`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:181 +msgid "For the following days, they are named with their dates, and then compressed. Use the command :command:`grep` and :command:`zgrep` (for the compressed ones) to search through the files." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:185 +msgid "For more information on logs and how to access them via the Odoo.sh dashboard, see :ref:`this administration documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:188 +msgid "For more information on accessing logs via the command line visit :ref:`this developer documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:191 +msgid "**Odoo Online** users won't have access to the logs. However `Odoo Support `_ can be contacted if there is a recurring issue with the same client or domain." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:196 +msgid "Get help from Odoo support" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:198 +msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful when reaching out to the Odoo Support team about an issue:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:201 +msgid "Send a copy of the email headers. The `.EML` file (or **headers**) of the email is the file format containing all the technical information required for an investigation. The documentation from the email provider might explain how to access the EML file/header files. Once the headers of the email are obtained, adding it into the Odoo Support ticket is the most efficient way for the Odoo Support team to investigate." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:208 +msgid "`Gmail documentation on headers `_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:209 +msgid "`Outlook documentation on headers `_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:212 +msgid "Explain the exact flow that is being followed to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:215 +msgid "Is this a notification message from a reply being received in Odoo?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:216 +msgid "Is this a message being sent from the Odoo database?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:217 +msgid "Is there an incoming email server being used, or is the email somehow being redirected?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:218 +msgid "Is there an example of an email that has been correctly forwarded?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:220 +msgid "Provide answers to the following questions:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:222 +msgid "Is it a generic issue, or is it specific to a use case? If specific to a use case, which one exactly?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:224 +msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database, and display the :ref:`red envelope `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:228 +msgid "The bounce system parameter needs to be set in the technical settings in order for the database to correctly receive bounce messages. To access this setting, go to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`. Then select the parameter name :guilabel:`mail.bounce.alias` and set the value to `bounce` if it isn't already set." msgstr "" #: ../../content/applications/general/export_import_data.rst:3 diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 854eb44dd..51d72cd5a 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-11 16:10+0000\n" +"POT-Creation-Date: 2023-10-09 08:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -366,7 +366,6 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:88 #: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:14 -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:14 #: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:16 #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:51 #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:16 @@ -1288,6 +1287,7 @@ msgid "To change the day, click the :guilabel:`31`, and change it to a day withi msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:194 +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:115 msgid "Then, to change the month, click :guilabel:`December` to reveal the drop-down menu, and select the desired month." msgstr "" @@ -1352,35 +1352,123 @@ msgid "Cycle counts" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:5 -msgid "In most companies, the stock is only counted once a year. That's why by default, after making an inventory adjustment in Odoo, the scheduled date for the next count is set on the 31st of December. However, for some businesses it's crucial to have an accurate inventory count at all times." +msgid "For most companies, warehouse stock only needs to be counted once a year. This is why, by default, after making an *inventory adjustment* in Odoo, the scheduled date for the next inventory count is set for the 31st of December of the current year." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:10 -msgid "The goal of cycle counts is to keep critical stock levels accurate by counting more often at key locations." +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:9 +msgid "However, for some businesses, it's crucial to have an accurate inventory count at all times. These companies use *cycle counts* to keep critical stock levels accurate. Cycle counting is a method by which companies count their inventory more often in certain *locations*, to ensure that their physical inventory counts match their inventory records." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:16 -msgid "In Odoo, cycle counts are location-based. The frequency of the counts is defined by the storage location. To activate storage locations, go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse` and activate the :guilabel:`Storage Locations` setting. Next, click :guilabel:`Save` to apply the setting." +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:15 +msgid "Activate storage locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:17 +msgid "In Odoo, cycle counts are location-based. Therefore, the *storage locations* feature needs to be enabled before performing a cycle count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:20 +msgid "To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Then, click the checkbox next to :guilabel:`Storage Locations`. Click :guilabel:`Save` to save all changes." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 -msgid "Enable Storage Locations in Odoo settings." +msgid "Enabled storage locations setting in inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:26 -msgid "Change the inventory frequency" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:28 -msgid "To change a location's inventory frequency, first, go to the locations by clicking :menuselection:`Inventory --> Configuration --> Locations`." +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:29 +msgid "Change inventory count frequency by location" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:31 -msgid "Then, click on a location to open the location settings. Next, click on :guilabel:`Edit`. In the :guilabel:`Inventory Frequency (Days)` field, set the number of days. For example, a location that needs an inventory count every 30 days would set the :guilabel:`Inventory Frequency (Days)` value to `30`. Once the value is entered, click :guilabel:`Save` to apply the setting to the location. Now, once an inventory adjustment is applied to this location, the next scheduled count date will be automatically set based on the number of days in the :guilabel:`Inventory Frequency (Days)` setting." +msgid "Now that the storage locations setting is enabled, the inventory count frequency can be changed for specific locations created in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:34 +msgid "To view and edit locations, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. This reveals a :guilabel:`Locations` page containing every location currently created and listed in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:38 +msgid "From this page, click into a location to reveal the settings and configuration page for that location. Click :guilabel:`Edit` to edit the location settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:41 +msgid "Under the :guilabel:`Cyclic Inventory` section, locate the :guilabel:`Inventory Frequency (Days)` field, which should be set to `0` (if this location has not been edited previously). In this field, change the value to whichever number of days is desired." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 -msgid "Edit a location to change the inventory frequency." +msgid "Location frequency setting on location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:50 +msgid "A location that needs an inventory count every 30 days should have the :guilabel:`Inventory Frequency (Days)` value set to `30`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:53 +msgid "Once the frequency has been changed to the desired number of days, click :guilabel:`Save` to save changes. Now, once an inventory adjustment is applied to this location, the next scheduled count date is automatically set, based on the value entered into the :guilabel:`Inventory Frequency (Days)` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:59 +msgid "Count inventory by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:61 +msgid "To perform a cycle count for a specific location in the warehouse, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`. This reveals an :guilabel:`Inventory Adjustments` page containing all products currently in stock, with each product listed on its own line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:66 +msgid "From this page, the :guilabel:`Filters` and :guilabel:`Group By` buttons (at the top of the page, under the :guilabel:`Search...` bar), can be used to select specific locations and perform inventory counts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 +msgid "Inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:74 +msgid "To select a specific location and view all products within that location, click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to reveal a new drop-down menu to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:77 +msgid "Click :guilabel:`Location` from the drop-down menu, then click :guilabel:`Apply`. The page now displays condensed drop-down menus of each location in the warehouse that has products in stock, and a cycle count can be performed for all products in that location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:82 +msgid "In large warehouses with multiple locations and a high volume of products, it might be easier to search for the specific location desired. To do this, from the :guilabel:`Inventory Adjustments` page, click :guilabel:`Filters`. Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right. Click this menu to reveal three drop-downs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:87 +msgid "For the first field, click and select :guilabel:`Location` from the drop-down. For the second field, leave the :guilabel:`contains` value as is. For the third field, type in the name of the location that is being searched for. Click :guilabel:`Apply` for that location to appear on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 +msgid "Applied filters and group by on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:97 +msgid "Change full inventory count frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:99 +msgid "While cycle counts are typically performed per location, the scheduled date for full inventory counts of everything in-stock in the warehouse can also be manually changed to push the date up sooner than the date listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:103 +msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting field, which includes a drop-down that is set to `31` :guilabel:`December` by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 +msgid "Frequency field in inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:112 +msgid "To change the day, click the `31`, and change it to a day within the range `1-31`, depending on the desired month of the year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:118 +msgid "Once all changes have been made, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:121 +msgid ":doc:`/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers.rst:5 @@ -7701,6 +7789,191 @@ msgstr "" msgid "Kits are primarily used to bundle components together for organization or sale. To manage multi-level products that require manufactured sub-components, refer to :doc:`this documentation ` on sub-assemblies." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:3 +msgid "Manufacturing backorders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:5 +msgid "In some cases, the full quantity of a manufacturing order cannot be produced immediately. When this happens, Odoo *Manufacturing* allows for the manufacturing of partial quantities of the order and creates a *backorder* for the remaining amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:9 +msgid "In the *Manufacturing* app, creating a backorder splits the original manufacturing order into two orders. The reference tag for each order is the tag used for the original order, followed by a hyphen and then an additional number to indicate that it's a backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:14 +msgid "A company creates a manufacturing order with the reference tag *WH/MO/00175*, for 10 units of *Product X*. After starting work on the manufacturing order, the employee working the production line realizes there are only enough components in stock to produce five units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:18 +msgid "Instead of waiting for additional stock of the components, they manufacture five units and create a backorder for the remaining five. This splits the manufacturing order into two separate orders: *WH/MO/00175-001* and *WH/MO/00175-002*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:22 +msgid "Order *001* contains the five units that have been manufactured, and is immediately marked as :guilabel:`Done`. Order *002* contains the five units that still need to be manufactured and is marked as :guilabel:`In Progress`. Once the remaining components are available, the employee returns to order *002* and manufactures the remaining units before closing the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:28 +msgid "Create a manufacturing backorder" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:30 +msgid "To create a backorder for part of a manufacturing order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order with a quantity of two or more or create one by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:34 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:86 +msgid "If a new manufacturing order is created, select a product from the :guilabel:`Product` drop-down menu and enter a quantity of two or more in the :guilabel:`Quantity` field, then click :guilabel:`Confirm` to confirm the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:38 +msgid "After manufacturing the quantity that is being produced immediately, enter that number in the :guilabel:`Quantity` field at the top of the manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 +msgid "The quantity field on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:45 +msgid "Next, click :guilabel:`Validate`, and a :guilabel:`You produced less than initial demand` pop-up window appears, from which a backorder can be created. Click :guilabel:`Create Backorder` to split the manufacturing order into two separate orders, with the reference tags *WH/MO/XXXXX-001* and *WH/MO/XXXXX-002*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 +msgid "The Create Backorder button on the \"You produced less than initial demand\" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:54 +msgid "Order *001* contains the items that have been manufactured, and is closed immediately. Order *002* is the backorder that contains the items that have yet to be manufactured, and remains open, to be completed at a later date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:58 +msgid "Once the remaining units can be manufactured, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select the backorder manufacturing order. If all of the remaining units are manufactured immediately, simply click :guilabel:`Validate` to close the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:63 +msgid "If only some of the remaining units are manufactured immediately, create another backorder for the remainder by following the steps detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:67 +msgid "Create a backorder from tablet view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:69 +msgid "Backorders for manufacturing orders can also be created from the work order tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:72 +msgid "In order to use tablet view, the *Work Orders* setting must be enabled. To enable it, navigate to :menuselection:`Manufacturing --> Configuration --> Settings`. On the :guilabel:`Settings` page, enable the checkbox next to :guilabel:`Work Orders`, then click :guilabel:`Save` to save the change. This makes the :guilabel:`Work Orders` tab appear on manufacturing orders, from which the tablet view can be opened." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:0 +msgid "The Work Orders setting on the Manufacturing settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:82 +msgid "To create a backorder from the tablet view, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order with a quantity of two or more or create one by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:90 +msgid "After confirming the manufacturing order, select the :guilabel:`Work Orders` tab and click the :guilabel:`📱 (tablet view)` button located on the line of the first work order to enter the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 +msgid "The tablet view button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:97 +msgid "Once in tablet view, enter the quantity being manufactured immediately in the :guilabel:`Units` field at the top left of the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 +msgid "The Units field in the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:104 +msgid "The steps for the rest of the workflow depend on whether the manufacturing order being processed requires the completion of a single work order or multiple work orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:108 +msgid "Single work order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:110 +msgid "If the manufacturing order only requires the completion of a single work order, complete the work order, then click :guilabel:`Mark As Done And Close MO`. The manufacturing order is closed and a backorder for the units that still need to be manufactured is created automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 +msgid "The Mark As Done And Close MO button in the tablet view of a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:118 +msgid "Once the remaining units are ready to be manufactured, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then select the backorder manufacturing order, which is titled using the reference tag of the original backorder with *002* added to the end." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:122 +msgid "On the backorder manufacturing order, select the :guilabel:`Work Orders` tab and click the :guilabel:`📱 (tablet view)` button located on the line of the work order to open the tablet view. If all of the units in the backorder will be completed immediately, simply click :guilabel:`Mark As Done And Close MO` after completing the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:127 +msgid "If only some of the remaining units will be manufactured immediately, enter the number in the :guilabel:`Units` field at the top left of the tablet view, then click :guilabel:`Mark As Done And Close MO` to create another backorder for the remaining units. The new backorder can be processed using the steps detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:133 +msgid "Multiple work orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:135 +msgid "If the manufacturing order requires the completion of multiple work orders, complete the first work order, and then click :guilabel:`Record Production`. This splits the manufacturing order into two separate orders, titled *WH/MO/XXXXX-001* and *WH/MO/XXXXX-002*, with *XXXXX* being the number of the original order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 +msgid "The Record Production button on a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:144 +msgid "The tablet view defaults to showing the first work order for the *002* manufacturing order. Since this manufacturing order will not be completed immediately, back out of tablet view by clicking the :guilabel:`⬅️ (back)` button twice. Doing so will take you to the *001* order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:148 +msgid "To finish the *001* order, select the :guilabel:`Work Orders` tab and click the :guilabel:`tablet view` button located on the line of the next work order. Finally, complete the remaining work orders, then click :guilabel:`Mark As Done And Close MO` to close the manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:152 +msgid "Once the remaining units are ready to be manufactured, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then select the *002* order. Select the :guilabel:`Work Orders` tab and click the :guilabel:`tablet view` button located on the line of the first work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:157 +msgid "If all of the units in the backorder will be completed immediately, simply click :guilabel:`Mark As Done And Close MO` after completing all of the work orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:160 +msgid "If only some of the remaining units will be manufactured immediately, enter the number in the :guilabel:`Units` field at the top left of the tablet view, then click :guilabel:`Record Production` to create an additional backorder for the remaining units, with *003* at the end of its reference tag." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:165 +msgid "The *002* backorder and *003* backorder can be completed by following the steps detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:169 +msgid "It is also possible to create a backorder in the middle of a manufacturing order, when some but not all of the work orders have already been completed. Doing so marks the completed work order(s) as :guilabel:`Finished` on the backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:174 +msgid "A manufacturing order for four chairs requires the completion of two work orders: *Paint* and *Assemble*. While the paint step can be completed immediately for all four chairs, there are only enough screws to assemble two of them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:178 +msgid "As a result, the employee responsible for producing the chairs begins by painting all four, and marking the *Paint* work order as :guilabel:`Finished` for all of them. Then, they move on to the *Assemble* work order. They assemble two of the four chairs, enter that number in the :guilabel:`Units` field of the tablet view, and click :guilabel:`Record Production`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:183 +msgid "A backorder manufacturing order is created for the remaining two chairs. On the backorder, the *Paint* work order is already marked as :guilabel:`Finished`, and only the *Assemble* work order is left to be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:187 +msgid "Once more screws are available, the manufacturing employee assembles the remaining chairs and clicks :guilabel:`Mark As Done And Close MO` to complete the *Assemble* work order and close the backorder manufacturing order." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3 msgid "Managing BoMs for product variants" msgstr "" diff --git a/locale/sources/legal.pot b/locale/sources/legal.pot index 4ffb58211..ab23e8ffd 100644 --- a/locale/sources/legal.pot +++ b/locale/sources/legal.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-10-09 08:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2188,7 +2188,7 @@ msgid "4.1 Service de correction de Bugs" msgstr "" #: ../../content/legal/terms/i18n/enterprise_fr.rst:143 -msgid "Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts raisonnables pour corriger tout Bug du Logiciel ou des Modules Supplémentaires Couverts qui pourrait être signalé par le Client en suivant la procédure appropriée (généralement par le biais du formulaire en ligne ou des numéros de téléphone indiqués sur http://www.odoo.com.help, ou en cas de travail avec un Partenaire Odoo, le canal prévu par le partenaire), et de commencer à traiter ces signalements du Client dans un délai de 2 jours ouvrables." +msgid "Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts raisonnables pour corriger tout Bug du Logiciel ou des Modules Supplémentaires Couverts qui pourrait être signalé par le Client en suivant la procédure appropriée (généralement par le biais du formulaire en ligne ou des numéros de téléphone indiqués sur http://www.odoo.com/help, ou en cas de travail avec un Partenaire Odoo, le canal prévu par le partenaire), et de commencer à traiter ces signalements du Client dans un délai de 2 jours ouvrables." msgstr "" #: ../../content/legal/terms/i18n/enterprise_fr.rst:150 @@ -3382,7 +3382,7 @@ msgid "4.1 Serviço de Correção de Bugs" msgstr "" #: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:136 -msgid "Durante a vigência deste Contrato, a Odoo SA se compromete a realizar todos os esforços razoáveis para corrigir qualquer Bug do Software e Módulos Extras Cobertos relatados pelo Cliente por meio de um canal apropriado (normalmente, o formulário da Web ou os números de telefone listados em http://www.odoo.com.help, ou, ao trabalhar com um parceiro Odoo, o canal fornecido pelo parceiro) e começar a lidar com essas solicitações do Cliente em 2 dias úteis." +msgid "Durante a vigência deste Contrato, a Odoo SA se compromete a realizar todos os esforços razoáveis para corrigir qualquer Bug do Software e Módulos Extras Cobertos relatados pelo Cliente por meio de um canal apropriado (normalmente, o formulário da Web ou os números de telefone listados em http://www.odoo.com/help, ou, ao trabalhar com um parceiro Odoo, o canal fornecido pelo parceiro) e começar a lidar com essas solicitações do Cliente em 2 dias úteis." msgstr "" #: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:142 @@ -4950,6 +4950,134 @@ msgstr "" msgid "10 Annexe A : Licence Odoo Enterprise Edition" msgstr "" +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:5 +msgid "Allgemeine Verkaufsbedingungen" +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:9 +msgid "`PDF herunterladen `_" +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:11 +msgid "Letzte Änderung: 12. September 2023." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:13 +msgid "Diese Allgemeinen Verkaufsbedingungen regeln den Verkauf von Produkten und Dienstleistungen durch Odoo S.A. und seine verbundenen Unternehmen (zusammen \"Odoo SA\") an den Kunden. Für von Odoo S.A. erbrachte Dienstleistungen können zusätzliche Bedingungen gelten (z. B. der Enterprise-Abonnementvertrag). Falls diese zusätzlichen Bedingungen im Widerspruch zu den Allgemeinen Verkaufsbedingungen stehen, haben die zusätzlichen Bedingungen Vorrang vor diesen Allgemeinen Verkaufsbedingungen." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:21 +msgid "Bitte lesen Sie diese Bedingungen sorgfältig durch, bevor Sie eine Bestellung bei Odoo S.A. aufgeben. Durch die Annahme einer Bestellung bei Odoo S.A. erklärt der Kunde seine Zustimmung zu diesen Bedingungen." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:25 +msgid "Der Kunde verzichtet ausdrücklich auf seine eigenen Standardgeschäftsbedingungen, auch wenn diese nach diesen Standardgeschäftsbedingungen des Verkaufs erstellt wurden. Damit eine Abweichung gültig ist, muss sie im Voraus schriftlich vereinbart werden." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:30 +msgid "Unsere Rechnungen sind innerhalb von 21 Arbeitstagen zahlbar, sofern auf der Rechnung oder der Bestellung keine andere Zahlungsfrist angegeben ist. Bei Nichtzahlung bis zum Fälligkeitsdatum behält sich Odoo S.A. das Recht vor, eine pauschale Verzugszinszahlung in Höhe von 15% des noch ausstehenden Betrags zu verlangen. Odoo S.A. ist berechtigt, bei verspäteter Zahlung ohne vorherige Ankündigung die Erbringung von Dienstleistungen auszusetzen." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:37 +msgid "Ist eine Zahlung mehr als sechzig (60) Tage nach dem Fälligkeitsdatum noch ausstehend, behält sich Odoo S.A. das Recht vor, die Dienste eines Inkassounternehmens in Anspruch zu nehmen. Alle rechtlichen Kosten gehen zu Lasten des Kunden." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:42 +msgid "In bestimmten Ländern wird nach den internen Gesetzen Quellensteuer auf den Rechnungsbetrag erhoben. Jegliche Quellensteuer ist vom Kunden an die Steuerbehörden zu zahlen. Odoo S.A. kann unter keinen Umständen in Kosten im Zusammenhang mit den Gesetzen eines Landes verwickelt werden. Der Rechnungsbetrag ist daher vollständig an Odoo S.A. zu zahlen und enthält keine Kosten im Zusammenhang mit den Gesetzen des Landes, in dem sich der Kunde befindet." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:50 +msgid "Für Kunden mit globaler Präsenz erfolgt die Anwendung der Preise immer auf der Grundlage des Standorts des Kunden mit der höchsten Preisliste, sofern nicht schriftlich zum Zeitpunkt des Kaufs anders vereinbart." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:54 +msgid "Monatliche Abonnements sind nur für die Nutzung auf der Cloud-Plattform (Odoo SaaS und Odoo SH) verfügbar. Die Zahlung von monatlichen Abonnements kann nur per Kreditkarte oder einem gleichwertig unterstützten automatischen Lastschriftverfahren erfolgen. Odoo S.A. behält sich das Recht vor, ein monatliches Abonnement abzulehnen, das diesen Bedingungen nicht entspricht." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:60 +msgid "Odoo S.A. verpflichtet sich, sein Bestes zu tun, um die Dienstleistungen rechtzeitig gemäß den vereinbarten Zeitplänen bereitzustellen. Keine seiner Verpflichtungen kann jedoch als Verpflichtung zur Erzielung von Ergebnissen angesehen werden. Odoo S.A. kann unter keinen Umständen vom Kunden verlangt werden, als Dritter im Rahmen einer Schadensersatzklage aufzutreten, die gegen den Kunden von einem Endverbraucher eingereicht wird." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:67 +msgid "Damit sie zulässig ist, muss Odoo S.A. über jede Beanstandung innerhalb von 8 Tagen nach Lieferung der Waren oder Erbringung der Dienstleistungen per Einschreiben an seinen Geschäftssitz informiert werden." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:71 +msgid "Soweit gesetzlich zulässig, wird die Gesamthaftung jeder Partei zusammen mit ihren Tochtergesellschaften 50% des Gesamtbetrags, den der Kunde unter diesen Bedingungen in den 12 Monaten unmittelbar vor dem Ereignis, das zu einer solchen Klage geführt hat, gezahlt hat, nicht überschreiten. Mehrere Ansprüche vergrößern diese Begrenzung nicht." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:77 +msgid "Odoo S.A. behält sich das Recht vor, diese Bedingungen jederzeit ohne vorherige Ankündigung zu ändern. Der Kunde unterliegt den zum Zeitpunkt der Zustimmung geltenden Bedingungen." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:81 +msgid "Alle unsere vertraglichen Beziehungen unterliegen ausschließlich dem belgischen Recht. Darüber hinaus unterliegt jeder Streitfall ausschließlich der Zuständigkeit der Gerichte des Arrondissements Nivelles (Belgien)." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:5 +msgid "Términos Generales de Venta" +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:9 +msgid "`Descargar PDF `_" +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:11 +msgid "Última revisión: 12 de septiembre de 2023." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:13 +msgid "Estos Términos Generales de Venta rigen la venta de productos y servicios por parte de Odoo S.A. y sus filiales (en adelante denominadas conjuntamente \"Odoo S.A.\") al cliente. Para los servicios proporcionados por Odoo S.A., pueden aplicarse términos adicionales (por ejemplo, el Acuerdo de suscripción de Odoo Enterprise). Si estos términos adicionales son inconsistentes con los Términos Generales de Venta, prevalecerán sobre estos Términos Generales de Venta." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:20 +msgid "Lea estos términos detenidamente antes de realizar un pedido a Odoo S.A. Al aceptar un pedido con Odoo S.A., el cliente manifiesta su aceptación de estos términos." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:24 +msgid "El cliente renuncia explícitamente a sus propias condiciones y términos estándar, incluso si estos se redactaron después de estos términos y condiciones estándar de venta. Para que una derogación sea válida, debe acordarse expresamente por adelantado por escrito." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:29 +msgid "Nuestras facturas son pagaderas en un plazo de 21 días laborables, a menos que en la factura o el pedido se indique otro plazo de pago. En caso de falta de pago en la fecha de vencimiento, Odoo S.A. se reserva el derecho de solicitar un pago de intereses fijos del 15% sobre la suma pendiente. Odoo S.A. estará autorizada a suspender la prestación de servicios sin previo aviso en caso de retraso en el pago." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:36 +msgid "Si un pago aún está pendiente más de sesenta (60) días después de la fecha de vencimiento, Odoo S.A. se reserva el derecho de recurrir a los servicios de una empresa de recuperación de deudas. Todos los gastos legales serán a cargo del cliente." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:41 +msgid "En algunos países se aplica la retención en la fuente sobre el monto de las facturas, de acuerdo con su legislación interna. Cualquier retención en la fuente será pagada por el cliente a las autoridades fiscales. En ningún caso Odoo S.A. podrá involucrarse en los costos relacionados con la legislación de un país. El monto de la factura, por lo tanto, será debido a Odoo S.A. en su totalidad y no incluye ningún costo relacionado con la legislación del país en el que se encuentra el cliente." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:49 +msgid "Para clientes con presencia global, la tarificación aplicable siempre se basa en la ubicación del cliente con la lista de precios más alta, a menos que se especifique lo contrario por escrito en el momento de la compra." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:53 +msgid "Las Suscripciones Mensuales solo están disponibles para alojamiento en la Plataforma en la Nube (Odoo SaaS y Odoo SH). El pago de las Suscripciones Mensuales solo puede realizarse con tarjeta de crédito o un método de débito automático equivalente admitido. Odoo S.A. se reserva el derecho de rechazar cualquier Suscripción Mensual que no cumpla con estas condiciones." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:59 +msgid "Odoo S.A. se compromete a hacer lo posible para suministrar los servicios a tiempo de acuerdo con los plazos acordados. Sin embargo, ninguna de sus obligaciones puede considerarse como una obligación de lograr resultados. Odoo S.A. no puede, bajo ninguna circunstancia, ser requerida por el cliente para aparecer como tercero en el contexto de cualquier reclamación por daños presentada contra el cliente por un consumidor final." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:66 +msgid "Para que sea admisible, Odoo S.A. debe ser notificada de cualquier reclamación mediante una carta enviada por correo certificado a su sede registrada dentro de los 8 días posteriores a la entrega de los bienes o la prestación de los servicios." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:71 +msgid "En la medida máxima permitida por la ley, la responsabilidad agregada de cada parte junto con sus filiales que surja no superará el 50% del monto total pagado por el Cliente en virtud de estos términos durante los 12 meses inmediatamente anteriores a la fecha del evento que dé lugar a dicha reclamación. Múltiples reclamaciones no ampliarán esta limitación." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:77 +msgid "Odoo S.A. se reserva el derecho de modificar estos términos en cualquier momento sin previo aviso. El cliente estará sujeto a los términos vigentes en el momento de la aceptación de dichos términos." +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:81 +msgid "Todas nuestras relaciones contractuales estarán reguladas exclusivamente por la ley belga. Además, cualquier disputa que pueda surgir estará sujeta exclusivamente a la jurisdicción de los tribunales del distrito de Nivelles (Bélgica)." +msgstr "" + #: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:5 msgid "Conditions Générales de Vente" msgstr "" @@ -4959,7 +5087,7 @@ msgid "`Download PDF msgstr "" #: ../../content/legal/terms/terms_of_sale.rst:11 -msgid "Last revision: October 20, 2021." +msgid "Last revision: September 12, 2023." msgstr "" #: ../../content/legal/terms/terms_of_sale.rst:13 @@ -5511,25 +5647,33 @@ msgid "If a payment is still outstanding more than sixty (60) days after the due msgstr "" #: ../../content/legal/terms/terms_of_sale.rst:40 -msgid "Certain countries apply withholding at source on the amount of invoices, in accordance with their internal legislation. Any withholding at source will be paid by the client to the tax authorities. Under no circumstances can Odoo S.A. become involved in costs related to a country's legislation. The amount of the invoice will therefore be due to Odoo S.A. in its entirety and does not include any costs relating to the legislation of the country in which the client is located. For clients with a global presence, the applicable pricing is always based on the client location with the highest price list, unless otherwise specified in writing at the time of purchase." +msgid "Certain countries apply withholding at source on the amount of invoices, in accordance with their internal legislation. Any withholding at source will be paid by the client to the tax authorities. Under no circumstances can Odoo S.A. become involved in costs related to a country's legislation. The amount of the invoice will therefore be due to Odoo S.A. in its entirety and does not include any costs relating to the legislation of the country in which the client is located." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:50 +#: ../../content/legal/terms/terms_of_sale.rst:48 +msgid "For clients with a global presence, the applicable pricing is always based on the client location with the highest price list, unless otherwise specified in writing at the time of purchase." +msgstr "" + +#: ../../content/legal/terms/terms_of_sale.rst:52 +msgid "Monthly Subscriptions are only available for hosting on the Cloud Platform (Odoo SaaS and Odoo SH). Payment of Monthly Subscriptions can only be made by credit card or an equivalent supported automatic debit method. Odoo S.A. reserves the right to refuse any Monthly Subscription that does not comply with these conditions." +msgstr "" + +#: ../../content/legal/terms/terms_of_sale.rst:58 msgid "Odoo S.A. undertakes to do its best to supply services in due time in accordance with the agreed timeframes. However, none of its obligations can be considered as being an obligation to achieve results. Odoo S.A. cannot, under any circumstances, be required by the client to appear as a third party in the context of any claim for damages filed against the client by an end consumer." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:56 +#: ../../content/legal/terms/terms_of_sale.rst:64 msgid "In order for it to be admissible, Odoo S.A. must be notified of any claim by means of a letter sent by recorded delivery to its registered office within 8 days of the delivery of the goods or the provision of the services." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:60 +#: ../../content/legal/terms/terms_of_sale.rst:68 msgid "To the maximum extent permitted by law, the aggregate liability of each party together with its affiliates arising will not exceed 50% of the total amount paid by the Customer under these terms during the 12 months immediately preceding the date of the event giving rise to such claim. Multiple claims shall not enlarge this limitation." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:66 +#: ../../content/legal/terms/terms_of_sale.rst:74 msgid "Odoo S.A. reserves the right to modify these terms at any time without prior notice. The client will be subject to the terms in force at the time of acceptation of those terms." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:70 +#: ../../content/legal/terms/terms_of_sale.rst:78 msgid "All our contractual relations will be governed exclusively by Belgian law. Moreover, any dispute that may arise will be subject exclusively to the jurisdiction of the courts of the Nivelles arrondissement (Belgium)." msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index f4235fed5..932cc4ee1 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-11 16:10+0000\n" +"POT-Creation-Date: 2023-10-09 08:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1430,7 +1430,7 @@ msgid "Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:43 -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:149 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:391 msgid "Cash drawer" msgstr "" @@ -1439,7 +1439,7 @@ msgid "The cash drawer should be connected to the printer with an RJ25 cable." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:45 -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:117 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:359 msgid "Barcode scanner" msgstr "" @@ -1596,42 +1596,386 @@ msgid "Epson and Star receipt printers and Zebra label printers do not need a dr msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:103 -msgid "The Zebra printer doesn't print anything" +msgid "Epson configuration special case" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:105 -msgid "Zebra printers are quite sensitive to the format of the Zebra Programming Language (ZPL) code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings --> Technical --> User Interface --> Views` in :ref:`developer mode ` and look for the corresponding template." +msgid "Most Epson printers support printing receipts in Odoo :abbr:`POS (Point of Sale)` using the `GS v 0` command. However, the following Epson printer models do not support this command:" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:112 -msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here `_." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:108 +msgid "TM-U220" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:120 -msgid "The characters read by the barcode scanner don't match the barcode" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:109 +msgid "TM-U230" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:122 -msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to the form view of the device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select the correct format." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:110 +msgid "TM-P60" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:111 +msgid "TMP-P60II" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:113 +msgid "Bypass this issue by configuring the printer to use the `ESC *` command instead." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:116 +msgid "Process to force ESC * command" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:119 +msgid "Epson printer compatibility" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:121 +msgid "The first step is to check whether the printer is incompatible with `GS v 0` command." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:125 +msgid "`Epson GS v 0 documentation `_ for `GS v 0` compatible printers." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:127 -msgid "Nothing happens when a barcode is scanned" +msgid "`Epson ESC * documentation `_ for `ESC *` compatible printers." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:129 -msgid "Make sure that the correct device is selected in the :menuselection:`Point of Sale` configuration and that the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode. To do so, navigate to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> Edit`." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:130 +msgid "If the printer is not compatible with the `ESC *` command then the following process is not possible. Should the printer be compatible to use the `ESC *` command to print, follow this process to configure the printer with the :abbr:`IoT (Internet of Things)` box." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:135 +msgid "IoT box configuration for ESC *" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:137 +msgid "To configure the :abbr:`IoT (Internet of Things)` box to use the `ESC *` command to print, go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to :menuselection:`IoT app --> IoT Boxes`. Then click on the :guilabel:`IP address` and this will direct to the :abbr:`IoT (Internet of Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:142 +msgid "**Choosing the printer**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:144 +msgid "Now click on the :guilabel:`Printers server` button. This will redirect the browser to the *CUPS* page. Next, go to :menuselection:`Administration --> Printers --> Add Printer`, choose the printer that should be modified, and then click :guilabel:`Continue`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:149 +msgid "If the name of the printer is still uncertain, take the following steps:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:151 +msgid "Take note of the listed printers on the *CUPS* page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 +msgid "Turn the printer off and refresh the page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:153 +msgid "Now compare the difference with the first list to see which printer disappeared." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154 +msgid "Turn the printer back on and refresh the page again." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:155 +msgid "Double-check the list again to see if the printer re-appears." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:156 +msgid "The printer that disappeared and reappears again on the listed printers is the name of the printer in question." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:160 +msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:162 +msgid "**CUPS naming convention**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:164 +msgid "`CUPS` will prompt the admin for three pieces of information: the :guilabel:`Name`, :guilabel:`Description` and the :guilabel:`Location`. The last two pieces of information do not need to be specific, however, the :guilabel:`Name` should follow a particular convention to work with the `ESC *` command." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:169 +msgid "The :guilabel:`Name` should match this convention: `__IMC___...___`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:172 +msgid "A breakdown of the naming convention:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:174 +msgid "`printer_name`: This is the printer name. It can be any character as long as it does not contain `_`, `/`, `#`, or ` ` (space character)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:176 +msgid "`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC *`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:177 +msgid "`param_1`: This stands for the specific parameter:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:179 +msgid "`SCALE`: Scale of the picture (with the same aspect ratio). `X` should be an integer describing the scale percentage that should be used." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:183 +msgid "`100` is the original size, `50` is half the size, `200` is twice the size." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:185 +msgid "`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not specified)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:186 +msgid "`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if not specified)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:189 +msgid "*Density* parameters might need to be configured in a particular way depending on the printer model." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:193 +msgid "Visit `Epson's ESC * documentation `_ and click on the printer model printer in the table above to see if the printer should set these parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:198 +msgid "The following are examples of proper and improper name formatting:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:200 +msgid "Proper name formatting:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:202 +msgid "`EPSONTMm30II__IMC__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:203 +msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:205 +msgid "Improper name formatting (this will not prevent printing, but the result might not have the expected printed output):" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:208 +msgid "`EPSON TMm 30II` -> The name can't have spaces." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:209 +msgid "`EPSONTMm30II` -> The name itself is correct, but it won't use `ESC *`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:210 +msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:211 +msgid "`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:212 +msgid "`EPSONTMm30II__IMC_SCALE__` -> The parameter `SCALE` is missing the scale value." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:214 +msgid "**Finish adding a printer**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:216 +msgid "After setting the name of the printer with the appropriate naming convention, click :guilabel:`Continue`. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:220 +msgid "After completing these steps, click :guilabel:`Add Printer`. If everything was done correctly, the page should redirect to the *Banners* page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:223 +msgid "At this point the printer should have been created, now the :abbr:`IoT (Internet of Things)` box just needs to detect it and then sync to Odoo's server (this could take a few minutes)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:226 +msgid "**Adding the printer to Odoo PoS**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:228 +msgid "Once the printer is visible on the Odoo database, don't forget to choose it in the :abbr:`PoS (Point of Sale)`configuration as the :abbr:`IoT (Internet of Things)` printer. Navigate to :menuselection:`Pos App --> Settings --> Connected Devices --> IoT Box --> Receipt Printer --> Save`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:234 +msgid "If the printer was set up incorrectly (it is still printing random text or the printed receipt is too big or small), then it cannot be modified via the printer name with *CUPS*. Instead, the above process can be repeated to set up another printer from scratch to create one with modified parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:239 +msgid "**Example setup of the Epson TM-U220B printer using ESC**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:244 +msgid "The following is an example of the troubleshooting process for a TM-U220B printer model using the `ESC *` command. The receipt pictured below is an example of a receipt that is printing correctly due to proper formatting (in theory):" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Properly formatted receipt picture from a demo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:252 +msgid "Trying to print this receipt right-away prior to the proper formatting will not work as the TM-U220B printer model does not support `GS v 0`. Instead random characters will print:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Printer paper with seemingly random characters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:259 +msgid "To properly configure formatting for the Epson TM-U220B printer model take the following steps." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:261 +msgid "After consulting Epson's website for compatibility for both of the commands: `GS v 0 `_ and `ESC * `_, it can be seen that indeed the TM-U220B is not compatible with `GS v 0`, but is compatible with `ESC *`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Epson compatibility evaluation from Epson website." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:270 +msgid "When adding the printer, *CUPS* will ask which printer should be added:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Administration menu, add printer selection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:276 +msgid "In this case, the printer is connected via :abbr:`USB (Universal Serial Bus)` so it won' be part of the :guilabel:`Discovered Network Printers`. Instead it is likely part of the :guilabel:`Unknown` selection under :guilabel:`Local Printers`. By unplugging the printer's :abbr:`USB (Universal Serial Bus)` cable from the :abbr:`IoT (Internet of Things)` box and refreshing the page, the :guilabel:`Unknown` printer disappears. By plugging it back in, the printer reappears, so it can be said that this is the printer in question." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:283 +msgid "For the naming convention, since it will need to print using the `ESC *` command, it is imperative to add `__IMC`. Reference the printer model on `Epson's ESC * site `_ to find out more about the *density* parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Epson TM-U220 specifications on manufacturer's website." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:292 +msgid "For this particular model, TM-U220, `m` should be equal to 0 or 1. While referencing the :guilabel:`Description` below the pink box in the above picture, the `m` values could be 0, 1, 32 or 33. So in this printers case, the `m` value can NOT be 32 or 33 (otherwise there will be random characters printed)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:297 +msgid "The table includes the numeric values: 32 and 33, they both occur if the :guilabel:`Number of bits for vertical data` is set to 24. This means that is a *High Vertical Density*. In the case of configuring the Epson TM-U220, the *Low Vertical Density* will need to be forced, as this printer model does not support *High Vertical Density* for this command `ESC *`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:302 +msgid "To add a *Low Vertical Density*, add the `LDV` parameter to the naming convention." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:308 +msgid "Click :guilabel:`Continue` to proceed. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Epson TM-U220 specifications on manufacturers website." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:315 +msgid "However when trying to print with the naming convention: `EpsonTMU220B__IMC_LDV__`, it will print the receipt, but it will be too big and outside the margin. To resolve this, add a new printer (and naming convention) with the `SCALE` parameter to adapt to our receipt size." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:319 +msgid "Here are some examples:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:324 +msgid "Printer Naming Convention" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:325 +msgid "`EpsonTMU220B__IMC_LDV__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:326 +msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:327 +msgid "`EpsonTMU220B__IMC_LDV_LDH__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:328 +msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt example format." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_SCALE75__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:346 +msgid "The Zebra printer doesn't print anything" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:348 +msgid "Zebra printers are quite sensitive to the format of the Zebra Programming Language (ZPL) code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings --> Technical --> User Interface --> Views` in :ref:`developer mode ` and look for the corresponding template." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:355 +msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:362 +msgid "The characters read by the barcode scanner don't match the barcode" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:364 +msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to the form view of the device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select the correct format." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:369 +msgid "Nothing happens when a barcode is scanned" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:371 +msgid "Make sure that the correct device is selected in the :menuselection:`Point of Sale` configuration and that the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode. To do so, navigate to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> Edit`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:377 msgid "The barcode scanner is detected as a keyboard" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:138 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:380 msgid "Some barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:141 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:383 msgid "The device type can be manually changed by going to its form view (:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the :guilabel:`Is scanner` option." msgstr "" @@ -1639,11 +1983,11 @@ msgstr "" msgid "Modifying the form view of the barcode scanner." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:394 msgid "The cash drawer does not open" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:396 msgid "The cash drawer should be connected to the printer and the :guilabel:`Cash drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer checkbox`." msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index 66a09668a..cc4377a9a 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-11 16:10+0000\n" +"POT-Creation-Date: 2023-10-09 08:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1448,10 +1448,12 @@ msgid "Windows 10 & Linux OS" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:191 msgid "Generate a self-signed certificate" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 msgid "Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to [IP address] (unsafe)`." msgstr "" @@ -1460,35 +1462,43 @@ msgid "warning page about the connection privacy on Google Chrome" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201 msgid "Warning page on Google Chrome, Windows 10" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:203 msgid "Then, sign in using your printer credentials to access the ePOS printer settings. To sign in, enter `epson` in the :guilabel:`ID` field and your printer serial number in the :guilabel:`Password` field." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:207 msgid "Click :guilabel:`Certificate List` in the :guilabel:`Authentication` section, and click :guilabel:`create` to generate a new **Self-Signed Certificate**. The :guilabel:`Common Name` should be automatically filled out. If not, fill it in with the printer IP address number. Select the years the certificate will be valid in the :guilabel:`Validity Period` field, click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the printer." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 msgid "The self-signed certificate is generated. Reload the page and click :guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure **Selfsigned Certificate** is correctly selected in the :guilabel:`Server Certificate` section." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218 msgid "Export a self-signed certificate" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220 msgid "The export process is heavily dependent on the :abbr:`OS (Operating System)` and the browser. Start by accessing your ePOS printer settings on your web browser by navigating to its IP address (e.g., `https://192.168.1.25`). Then, force the connection as explained in the **Generate a self-signed certificate tab**." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:225 msgid "If you are using **Google Chrome**," msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:227 msgid "click :guilabel:`Not secure` next to the search bar, and :guilabel:`Certificate is not valid`;" msgstr "" @@ -1497,19 +1507,24 @@ msgid "Connection to the printer not secure button in Google Chrome browser." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:233 msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:234 msgid "add `.crt` at the end of the file name to ensure it has the correct extension;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:235 msgid "select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom of the pop-up window;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:237 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:254 msgid "save, and the certificate is exported." msgstr "" @@ -1519,14 +1534,17 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:243 msgid "If you are using **Mozilla Firefox**," msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:245 msgid "click the **lock-shaped** icon on the left of the address bar;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:246 msgid "go to :menuselection:`Connection not secure --> More information --> Security tab --> View certificate`;" msgstr "" @@ -1535,10 +1553,12 @@ msgid "Connection is not secure button in Mozilla Firefox browser" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:252 msgid "scroll down to the :guilabel:`Miscellaneous` section;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:253 msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" msgstr "" @@ -1632,7 +1652,7 @@ msgid "Mac OS" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 -msgid "To secure the connection on a Mac:" +msgid "On Mac OS, you can secure the connection for all browsers by following these steps:" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 @@ -1648,42 +1668,118 @@ msgid "reboot the printer so you can use it with any other browser." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 +msgid "To generate and export an SSL certificate and send it to IOS devices, open **Google Chrome** or **Mozilla Firefox**. Then," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Warning page about the connection privacy on Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection to the printer not secure button in Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:240 +msgid "Make sure that the certificate ends with the extension `.crt`. Otherwise, some browsers might not find the file during the import process." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection is not secure button in Mozilla Firefox" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:256 msgid "Android OS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:258 msgid "To import an SSL certificate into an Android device, first create and export it from a computer. Next, transfer the `.crt` file to the device using email, Bluetooth, or USB. Once the file is on the device," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:262 msgid "open the settings and search for `certificate`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:263 msgid "click :guilabel:`Certificate AC` (Install from device storage);" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:194 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:264 msgid "select the certificate file to install it on the device." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:267 msgid "The specific steps for installing a certificate may vary depending on the version of Android and the device manufacturer." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:202 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:270 +msgid "iOS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:272 +msgid "To import an SSL certificate into an iOS device, first create and export it from a computer. Then, transfer the `.crt` file to the device using email, Bluetooth, or any file-sharing service." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:276 +msgid "Downloading this file triggers a warning pop-up window. Click :guilabel:`Allow` to download the configuration profile, and close the second pop-up window. Then," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:279 +msgid "go to the **Settings App** on the iOS device;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:280 +msgid "click :guilabel:`Profile Downloaded` under the user's details box;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:281 +msgid "locate the downloaded `.crt` file and select it;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:282 +msgid "click :guilabel:`Install` on the top right of the screen;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:283 +msgid "if a passcode is set on the device, enter the passcode;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:284 +msgid "click :guilabel:`Install` on the top right of the certificate warning screen and the pop-up window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:286 +msgid "click :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:290 +msgid "The certificate is installed, but it still needs to be authenticated. To do so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:292 +msgid "go to :menuselection:`Settings --> General --> About > Certificate Trust Settings`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:293 +msgid "enable the installed certificate using the **slide button**;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:294 +msgid "click :guilabel:`Continue` on the pop-up window." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:297 msgid "If you need to export SSL certificates from an operating system or web browser that has not been mentioned, search for `export SSL certificate` + `the name of your browser or operating system` in your preferred search engine." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:205 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:300 msgid "Similarly, to import SSL certificates from an unmentioned OS or browser, search for `import SSL certificate root authority` + `the name of your browser or operating system` in your preferred search engine." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:210 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:305 msgid "Check if the certificate was imported correctly" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:212 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:307 msgid "To confirm your printer's connection is secure, connect to its IP address using HTTPS. For example, navigate to `https://192.168.1.25` in your browser. If the SSL certificate has been applied correctly, you should no longer see a warning page, and the address bar should display a padlock icon, indicating that the connection is secure." msgstr "" @@ -3611,7 +3707,7 @@ msgid "In addition, for your B2B clients, it is currently required to manually r msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:92 -msgid "For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: invoices created from Amazon sales orders are **not** synchronized with TaxCloud, since Amazon already includes them in its own tax report to TaxCloud." +msgid "For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: invoices created from Amazon sales orders are **not** synchronized with TaxCloud, since Amazon already includes them in its own tax report to TaxCloud. (decommissioning TaxCloud integration in Odoo 17+)" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:97 diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index e4a19047d..4fc1fe41d 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-11 16:10+0000\n" +"POT-Creation-Date: 2023-10-09 08:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -136,23 +136,43 @@ msgid "Manage my products" msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:3 -msgid "How to display several images per product" +msgid "Multiple images per product" msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:5 -msgid "By default your product web page displays the main image of your product only. If you like to show your products under several angles, you can turn the image into a carrousel." +msgid "When you register several images for a product, only the first image is shown on the main products page. By clicking on the product, visitors can see additional images with the carousel view." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:11 -msgid "Check *Several images per product* in :menuselection:`Website Admin --> Configuration --> Settings`." +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:-1 +msgid "Showing the carousel view." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:13 -msgid "Open a product detail form and upload images from *Images* tab. Hit *Create* in Edit mode to get the upload wizard." +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:12 +msgid "Adding multiple images to a product" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:19 -msgid "Such extra image are common to all the product variants (if any)." +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:14 +msgid "Go to :menuselection:`Website --> Products`, and select a product." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:15 +msgid "Go to the :guilabel:`Sales` tab, click :guilabel:`Edit`, and :guilabel:`Add a media`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:16 +msgid "Click the pencil icon to add an image, then click :guilabel:`Save & New` to add additional ones." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:17 +msgid "Click :guilabel:`Save & Close` when you are done." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:-1 +msgid "Creating extra product media." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:23 +msgid "Such extra images are common to all the product variants (if any)." msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:3