odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/finance/fiscal_localizations/jordan.md

@@ -0,0 +1,250 @@
+---
+title: "Jordan"
+source_url: "https://docs.odoo.sbggai.top/applications/finance/fiscal_localizations/jordan.html"
+---
+
+======
+# Jordan
+
+.. _localizations_jordan/configuration/modules:
+
+# Modules
+
+The following modules are installed automatically with the Jordanian localization:
+
+.. list-table::
+   :header-rows: 1
+   :widths: 25 25 50
+
+   * - Name
+     - Technical name
+     - Description
+   * - :guilabel:`Jordan - Accounting`
+     - `l10n_jo`
+     - Jordanian :ref:`fiscal localization package <fiscal_localizations/packages>`, complete with
+       the Jordanian chart of accounts, taxes, tax report, and fiscal positions
+   * - :guilabel:`Jordan E-Invoicing`
+     - `l10n_jo_edi`
+     - Integration module for JoFotara to support Jordanian e-invoicing requirements
+
+> **note**:
+>    In some cases, such as when upgrading to a version with additional modules, it is possible that
+   modules may not be installed automatically. Any missing modules can be manually :ref:`installed
+   <general/install>`.
+
+.. seealso::
+   :doc:`Jordan Payroll localization documentation <../../hr/payroll/payroll_localizations/jordan>`
+
+.. _localizations/jordan/specifics:
+
+# Localization overview
+
+The Jordanian localization package ensures compliance with Jordanian fiscal and accounting
+regulations. It includes tools for managing taxes, fiscal positions, reporting, and a predefined
+chart of accounts tailored to Jordan's standards.
+
+The Jordanian localization package provides the following key features to ensure compliance with
+local fiscal and accounting regulations:
+
+- :doc:`../accounting/get_started/chart_of_accounts`: a predefined structure tailored to Jordanian
+  accounting standards
+- :ref:`localizations/jordan/taxes`: pre-configured tax rates, including standard VAT, zero-rated,
+  and exempt options
+- :doc:`../accounting/taxes/fiscal_positions`: automated tax adjustments based on customer or
+  supplier registration status
+- :ref:`localizations/jordan/tax-reporting`: detailed overview of your net tax liability
+- :ref:`E-invoicing (JoFotara)<localizations/jordan/jofotara>`: integration for electronic invoicing
+  in line with Jordanian government requirements
+
+.. _localizations/jordan/taxes:
+
+## Taxes
+
+The following :doc:`taxes <../accounting/taxes>` are available by default with the Jordanian
+localization package:
+
+- standard sales tax (16%): applied to most goods and services within Jordan.
+- exempt transactions: for sales and services not subject to VAT, such as financial services or
+  healthcare.
+- export tax (0%): zero-rated tax applied to goods and services exported outside Jordan.
+
+.. _localizations/jordan/tax-reporting:
+
+## Tax reporting
+
+The :doc:`VAT summary <../accounting/reporting/tax_returns>` provides a detailed breakdown of
+taxable, zero-rated, and exempt transactions. Like other :doc:`financial reports
+<../accounting/reporting>`, the VAT summary can be filtered by period, compared against other
+periods, and exported in Excel and PDF formats, ensuring compliance with Jordanian tax laws.
+
+.. _localizations/jordan/jofotara:
+
+# E-invoicing with JoFotara
+
+E-invoicing with JoFotara is integrated with Odoo, ensuring compliance with Jordanian government's
+technical and legal requirements for electronic invoicing. The JoFotara integration in Odoo directly
+connects with the Jordanian e-invoicing platform, allowing companies to:
+
+- generate compliant electronic invoices
+- submit invoices in real time for validation
+- track invoice statuses directly within Odoo
+
+The integration requires first creating an account with JoFotara, then generating API credentials,
+and finally entering those credentials in your Odoo database to link the two.
+
+.. _manuals: https://istd.gov.jo/EN/List/Electronic_billing_User_Manual
+
+[Government manuals ](manuals_) provide instructions for creating an account and generating the API
+credentials.
+
+.. _localizations/jordan/jofotara-configuration:
+
+## Configuration
+
+.. _localizations/jordan/linking-jofotara:
+
+### Link Odoo to JoFotara
+
+#. If you don't already have an account, create one by going to the [government manuals ](manuals_)
+   page and following the steps in the **Procedure Manual for Joining the Jordanian National
+   Electronic Invoicing System**.
+#. Generate API credentials (Activity Number, Secret Key, and Client ID) by going to the [government
+   manuals ](manuals_) page and following the steps in **Procedure Manual for Linking to the
+   Jordanian National Electronic Invoicing System**.
+#. In your Odoo database, go to :menuselection:`Accounting --> Configuration --> Settings`. In the
+   :guilabel:`Electronic Invoicing (Jordan)` section, enter the API credentials generated
+   previously:
+
+   - :guilabel:`Activity Number` (income source sequence)
+   - :guilabel:`JoFotara Secret Key`
+   - :guilabel:`JoFotara Client ID`
+
+#. Enter the :guilabel:`Taxpayer type`:
+
+   - :guilabel:`Unregistered in the sales tax`: for businesses not registered for sales tax. No tax
+     on the invoice line is required.
+   - :guilabel:`Registered in the sales tax`: for businesses registered under the standard sales tax
+     system. One tax computed as a percentage is required per invoice line.
+   - :guilabel:`Registered in the special sales tax`: for businesses subject to special sales tax
+     regulations. One tax computed as a percentage and one fixed tax per invoice line are required
+     per invoice.
+
+#. Click :guilabel:`Save`.
+
+> **tip**:
+>    If the :guilabel:`Electronic Invoicing (Jordan)` section is missing from the
+   :guilabel:`Settings`, make sure the :guilabel:`Jordan E-Invoicing` module is :ref:`installed
+   <general/install>`.
+
+.. _localizations/jordan/company-and-contacts:
+
+### Company and customers
+
+The JoFotara invoicing workflow requires address information related to the company that sends the
+invoices and the customers who receive them:
+
+#. Go to :menuselection:`Settings --> Users & Companies --> Companies` and select the company that
+   will use JoFotara.
+#. Fill in the :guilabel:`Company Name`, :guilabel:`Tax ID` (TIN), and :guilabel:`Country`. If
+   desired, fill in additional optional fields such as :guilabel:`Street`, :guilabel:`City`,
+   :guilabel:`State`, and :guilabel:`ZIP`.
+
+   > **important**:
+>       - The :guilabel:`Country` must be set to :guilabel:`Jordan`.
+      - The :guilabel:`Company Name` must match the name that is registered with the Income and
+        Sales Tax Department (ISTD).
+      - The company's :guilabel:`Currency` must be set to :guilabel:`JOD`.
+
+
+#. Go to :menuselection:`Accounting --> Customers --> Customers`.
+#. For each customer whose invoices will be sent to JoFotara, click on the customer to open the form
+   view, and complete the :guilabel:`Country` and :guilabel:`Tax ID`. If desired, fill in additional
+   optional fields such as :guilabel:`Street`, :guilabel:`City`, :guilabel:`State`, and
+   :guilabel:`ZIP`.
+
+.. _localizations/jordan/sending-invoices:
+
+## Sending invoices to JoFotara via Odoo
+
+Once the company has been :ref:`linked with JoFotara <localizations/jordan/linking-jofotara>` and
+the :ref:`company and customers have been properly configured
+<localizations/jordan/company-and-contacts>`, invoices can be sent to JoFotara via Odoo:
+
+#. Go to :menuselection:`Accounting --> Customers --> Invoices` and open a confirmed (posted)
+   invoice.
+#. Click :guilabel:`Send`.
+#. In the :guilabel:`Send` window, select :guilabel:`JoFotara (Jordan EDI)` and click
+   :guilabel:`Send`.
+
+When an invoice is sent to JoFotara, Odoo does the following:
+
+- generates the invoice in the required format (UBL 1.2)
+- submits the invoice to JoFotara for validation
+- receives the QR code from JoFotara on the invoice's PDF
+
+> **tip**:
+>    - Multiple invoices can be :ref:`sent at once <accounting/invoice/sending>` to JoFotara.
+   - From the :guilabel:`Invoices` list view, filter the invoices by their
+     :ref:`localizations/jordan/jofotara-state` to see the invoices that have either been sent or
+     not been sent to JoFotara.
+   - In the :icon:`oi-settings-adjust` (:guilabel:`adjust settings`) menu, add the
+     :guilabel:`JoFotara State` and :guilabel:`JoFotara Error[ fields to see the sending state and
+     any errors in the list view, respectively.
+
+> **important**:
+>    There is an inherent difference in how values are approximated in Odoo and ISTD due to the
+   differing system architectures. JOD values in Odoo are stored and approximated to three decimals,
+   whereas ISTD expects values to have nine decimals. As a result, an insignificant difference is
+   inevitable and arises between the values stores in Odoo and the values reported to ISTD, which
+   can have an error margin of ](0.001.
+
+.. _localizations/jordan/jofotara-state:
+
+### JoFotara State
+
+The :guilabel:`JoFotara State` field in the :guilabel:`Other Info` tab of confirmed invoices
+reflects the current state of the document in JoFotara. It can be changed manually to reflect the
+actual state of the invoices in cases where a technical error or timeout prevents Odoo from updating
+it automatically.
+
+.. _localizations/jordan/qr-codes:
+
+### Validating QR codes (Sanad app)
+
+To validate the QR code received from JoFotara on the invoice, follow these steps:
+
+#. Install the `Sanad app <https://www.sanad.gov.jo/Default/en).
+#. Navigate to :guilabel:`More`.
+#. Click on :guilabel:`Validate document` and scan the QR code.
+#. Review results.
+
+.. _localizations/jordan/debit-credit:
+
+### Debit and credit notes
+
+To send a debit or credit note to JoFotara, first create the :ref:`debit
+<accounting/credit_notes/issue-debit-note>` or :ref:`credit note
+<accounting/credit_notes/issue-credit-note>`. In the :guilabel:`Send` window, click
+:guilabel:`JoFotara (Jordan EDI)` to submit it for real-time validation. Upon successful validation,
+the QR code from JoFotara is embedded in the debit or credit note PDF.
+
+> **note**:
+>    Ensure that the :guilabel:`Reason` for generating a debit/credit note aligns with ISTD
+   regulations.
+
+.. _localizations/jordan/discounts:
+
+### Discounts
+
+JoFotara does not support negative quantities or negative prices on invoice lines. As a result,
+global discount and fixed amount discount functionality are not supported.
+
+Discounts must be applied **per invoice line as a percentage** instead of as a global discount or
+fixed amount.
+
+> **warning**:
+>    Attempting to submit invoices to JoFotara with negative invoice lines will result in validation
+   errors.
+
+.. seealso::
+   :ref:`Discount types <sales/discounts/discount-button>`

package/payload/skills/odoo18-docs/references/docs/applications/finance/fiscal_localizations/kenya.md

@@ -0,0 +1,361 @@
+---
+title: "Kenya"
+source_url: "https://docs.odoo.sbggai.top/applications/finance/fiscal_localizations/kenya.html"
+---
+
+=====
+# Kenya
+
+.. _localization/kenya/configuration:
+
+# Configuration
+
+Install the 🇰🇪 **Kenyan** :ref:`fiscal localization package <fiscal_localizations/packages>` to get
+all the features of the Kenyan localization.
+
+# eTIMS
+
+The [Kenya Revenue Authority (KRA) ](https://www.kra.go.ke/) has implemented the
+[electronic Tax Invoice Management System (eTIMS) ](https://www.kra.go.ke/online-services/etims)
+for tax collection.
+
+To submit documents through eTIMS, you must use an :abbr:`OSCU (Online Sales Control Unit)` that
+integrates with the existing **Trader Invoicing System (TIS)**, such as the one provided by Odoo.
+The OSCU is used to validate, encrypt, sign, transmit, and store tax invoices.
+
+> **note**:
+>    Make sure to :ref:`install <general/install>` the **Kenya eTIMS EDI** modules to use the OSCU
+   device fully.
+
+.. _kenya/initialization:
+
+## OSCU device initialization
+
+The OSCU must be initialized before use. To do so, navigate to :menuselection:`Settings --> General
+Settings`, click :guilabel:`Update Info` in the :guilabel:`Companies` section, and enter your
+:guilabel:`Tax ID`.
+
+To initialize the OSCU:
+
+#. Go to :menuselection:`Settings --> General Settings` and scroll down to the :guilabel:`Kenya
+   eTIMS Integration` section.
+#. Set the :guilabel:`eTIMS Server Mode` to :guilabel:`Test` for the initialization.
+#. Enter the :guilabel:`Serial Number` of the device and tick the two check boxes.
+#. Click :guilabel:`Initialize OSCU`.
+
+> **note**:
+>    Three server modes are available:
+
+   - :guilabel:`Demo`: Designed for demo purposes; it uses mock data and does not require an
+     initialized OSCU;
+   - :guilabel:`Test`: Used to test the connection to eTIMS;
+   - :guilabel:`Production`: Used for live databases that are ready to send data.
+
+> **Important**:
+>    If your device has **already been initialized** (through another ERP, for example), enable the
+   :doc:`../../general/developer_mode`. Then, in the :guilabel:`Kenya eTIMS Integration` section,
+   enter the ID of the unit in the :guilabel:`Unit ID` field and the key obtained through a previous
+   initialization in the :guilabel:`CMC Key` field. Click :guilabel:`Save` when done.
+
+Once the **OSCU module** has been :ref:`initialized <kenya/initialization>`, an OSCU serial number
+is generated for each company on that database with its **country** set to :guilabel:`Kenya`. The
+serial number is generated based on the VAT number of the company (regardless of its validity). It
+is a unique and sequential serial number starting with the prefix `ODOO` followed by the company's
+**VAT number** and a sequence of numbers.
+
+## Registering on eTIMS
+
+Taxpayers *must* sign up and create an account on the [KRA portal ](https://etims.kra.go.ke/basic/login/indexLogin).
+If you do not have an account yet:
+
+#. Sign up, enter your **PIN**, and verify that all information is correct, including your phone
+   number, email address, and postal address. Correct any errors on the [iTax page
+   ](https://itax.kra.go.ke/KRA-Portal/).
+#. An :abbr:`OTP (One-time Password)` is sent to the phone number provided. Unblock promotional
+   messages if you do not receive it.
+#. Upload the **business owner ID** *or* **director's ID** (as listed on iTax), along with the
+   filled-out and signed **commitment form** .
+#. On the **eTIMS dashboard**, click :guilabel:`Service request` at the top of the page. Select
+   :guilabel:`OSCU` as the **eTIMS type**, enter `Odoo KE LTD` as the third-party integrator, and
+   enter your company's OSCU serial number retrieved earlier.
+
+> **note**:
+>    Service request approvals are usually quick. If there's a delay, contact the eTIMS operation
+   or KRA office.
+
+.. admonition:: Commitment form
+
+   - Part 1: Fill in the taxpayer's information.
+   - Part 2: Fill in the business owner's *or* director's information.
+   - Part 3: Fill in your unique serial number found in Odoo.
+   - Part 4: Tick **OSCU**, enter Odoo KE LTD PIN `PO52112956W`, and enter the Odoo version you're
+     using (17.0 or onwards).
+   - Part 5: Check the mandatory boxes, enter a date, and sign.
+
+## eTIMS codes
+
+Common standard codes are **automatically** fetched from the KRA eTIMS API servers every two days.
+To fetch them manually, proceed as follows:
+
+#. Enable the :doc:`../../general/developer_mode`.
+#. Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for
+   :guilabel:`KE eTIMS: Fetch KRA standard codes`.
+#. Click the action in the list, then click :guilabel:`Run Manually` to fetch the codes.
+
+Go to :menuselection:`Accounting --> Configuration --> KE OSCU Codes` to view the complete list of
+fetched OSCU codes.
+
+.. image:: kenya/oscu-codes.png
+   :alt: List of fetched OSCU codes.
+
+.. _etims/unspsc:
+
+## UNSPSC codes
+
+The KRA needs UNSPSC codes for a product to be **registered**. UNSPSC codes are **automatically**
+fetched from the KRA eTIMS API servers every day. To fetch them manually, proceed as follows:
+
+#. Enable the :doc:`../../general/developer_mode`.
+#. Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for
+   :guilabel:`KE eTIMS: Fetch UNSPSC codes from eTIMS`.
+#. Click the action in the list, then click :guilabel:`Run Manually` to fetch the codes.
+
+Go to the **product form**, and in the :guilabel:`Accounting` tab, click the :guilabel:`UNSPSC
+Category` field to view the complete list of fetched UNSPSC codes.
+
+## Notices
+
+Notices are **automatically** fetched from the KRA eTIMS API servers every day. To fetch them
+**manually**, proceed as follows:
+
+#. Enable the :doc:`../../general/developer_mode`.
+#. Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for
+   :guilabel:`KE eTIMS: Fetch KRA notices from eTIMS`.
+#. Click the action in the list, then click :guilabel:`Run Manually` to fetch the notices.
+
+Go to :menuselection:`Accounting --> Configuration --> KE OSCU Notices` to view the complete list of
+fetched notices.
+
+## Multi-company
+
+.. _kenya/branch:
+
+.. seealso::
+   :doc:`../../general/companies`
+
+If you have :ref:`multiple companies <accounting/multi-company>`, you can centralize and manage them
+all on a single Odoo database. The KRA identifies and differentiates the **main** company from
+its **subsidiaries** by using IDs. Furthermore, subsidiaries are classified as **branches** of the
+main company.
+
+To configure the company's ID, open the **Settings** app, click :guilabel:`Update Info` in the
+:guilabel:`Companies` section, and search for the :guilabel:`eTIMS Branch Code` field. The **main
+company** has a branch ID equal to `00` in a multi-company environment. Companies that are *not* the
+main company have a branch ID other than `00` and are assigned an ID by the KRA.
+
+To add a branch, go to the :guilabel:`Branches` tab in the **company settings** and click
+:guilabel:`Add a line`.
+
+To fetch the **branch ID** from the KRA for your non-main companies, ensure the main company has a
+Kenyan :guilabel:`Tax ID` and the OSCU device has been :ref:`initialized <kenya/initialization>`.
+Then, go to the :guilabel:`Branches` tab and click :guilabel:`Populate from KRA`.
+
+> **note**:
+>    - The KRA considers each **place of supply** as a separate branch (ID).
+   - The **OSCU** device must be :ref:`initialized independently <kenya/initialization>` for each
+     branch.
+
+## Contact branch ID
+
+To attribute a branch ID to a contact, access the contact form, go to the :guilabel:`Accounting`
+tab, and enter the branch code in the :guilabel:`eTIMS Branch Code` field.
+
+> **note**:
+>    By default, contacts' branch IDs are set to `OO`.
+
+## KRA sequences
+
+> **important**:
+>    Odoo invoice sequences and KRA sequences are **different**.
+
+In Odoo, invoice sequences depend on the **main company**. Main companies can see the invoices of
+branches, but branches **cannot** see the main company's invoices or those of other branches.
+
+The KRA needs **independent** sequences per branch. Therefore, Odoo manages sequences individually
+per branch.
+
+.. example::
+   If you have a main company with two branches, the invoice sequence would be the following:
+
+   - Creating an invoice on **branch 1**: INV/2024/00001;
+   - Creating an invoice on **branch 2**: INV/2024/00002;
+   - Creating an invoice on the **main company**: INV/2024/00003.
+
+   This is how Odoo manages sequences to be compliant with the KRA regulations:
+
+   - Creating an invoice on **branch 1**: INV/2024/00001;
+   - Creating an invoice on **branch 2**: INV/2024/00001;
+   - Creating an invoice on the **main company**: INV/2024/00001.
+
+# Insurance
+
+For **health service providers**, you can send insurance information about the main and branch
+companies and update it in eTIMS. To do so, go to :menuselection:`Accounting --> Configuration -->
+Settings`, scroll to the :guilabel:`Kenya eTIMS Integration` section, and fill in the
+:guilabel:`Code`, :guilabel:`Name`, and :guilabel:`Rate` fields. Click :guilabel:`Send Insurance
+Details` when done.
+
+.. _kenya/product-registration:
+
+# Product registration
+
+The KRA requires **products to be registered** first before conducting business operations (such as
+stock movements, :abbr:`BOM (Bill of Materials)`, customer invoices, etc.). For a product to be
+registered, the following fields must be defined on the product form:
+
+- In the :guilabel:`General Information` tab: :guilabel:`Cost`.
+- In the :guilabel:`Accounting` tab:
+
+  - :guilabel:`Packaging Unit`;
+  - :guilabel:`Packaging Quantity`;
+  - :guilabel:`Origin Country`;
+  - :guilabel:`eTIMS Product Type`;
+  - :guilabel:`Insurance Applicable`;
+  - :ref:`UNSPSC Category <etims/unspsc>`.
+
+If the elements above are defined, the product is automatically registered while sending the
+operation to the KRA. If not, you will be alerted by a yellow banner at the top of the screen
+inviting you to check the missing elements.
+
+.. image:: kenya/product-registration.png
+   :alt: Product registration template.
+
+# Stock movements
+
+All **stock movements** must be sent to the KRA. They do not require an invoice if they are
+internal operations or stock adjustments; therefore, Odoo automatically sends them if at least one
+of the following conditions are met:
+
+#. No contact is set for the move;
+#. The contact is your main company or a branch of the main company.
+
+If the stock moves are **external operations** (e.g., to contacts that are not part of the main
+company or its branches), the stock moves are automatically sent *after* the invoice is sent to
+eTIMS.
+
+> **note**:
+>    - The stock move must be confirmed before sending the invoice to eTIMS.
+   - The product(s) must be :ref:`registered <kenya/product-registration>` for the stock move to be
+     sent to eTIMS. If the product has not been registered yet, a yellow banner will prompt the
+     products' registration.
+
+# Purchases
+
+Odoo automatically fetches new vendor bills from eTIMS every day. You need to confirm the fetched
+vendor bills and send the confirmation to the KRA. To confirm a vendor bill, it must be linked to
+one or several confirmed purchase order line(s).
+
+.. _kenya/purchases:
+
+In the case of purchases (not customs imports), the steps to link purchase order lines with bills
+are the following:
+
+#. Go to :menuselection:`Accounting --> Vendors --> Bills`.
+   The vendor bill is fetched from the KRA servers. The JSON file is available in the chatter of the
+   vendor bill if needed.
+#. Odoo looks at the :guilabel:`Tax ID` (PIN) of the vendor (partner);
+
+   - If it is unknown, a new contact (partner) is created.
+   - If it is known and the branch ID is the same, Odoo uses the known contact.
+
+#. In the fetched bill from the KRA, select the :guilabel:`Product`. Each vendor bill *must* contain
+   a product to be confirmed and sent to eTIMS later on.
+#. Odoo checks existing purchase order lines matching the product(s) entered at the previous step
+   and the partner (if any). Click the :guilabel:`Purchase Order Line` field, and select the correct
+   related purchase order line(s) matching the product(s). The quantities on the bill *must* be the
+   same as the received quantities indicated on the purchase order.
+
+   If no existing purchase order line matches the lines of the fetched bill, click
+   :guilabel:`Create Purchase Order` and create a purchase order based on the unmatched line(s).
+   :guilabel:`Validate` the resulting stock move and :guilabel:`Confirm` the bill.
+
+#. Set a method in the :guilabel:`eTIMS Payment Method` field..
+#. Once all steps are completed, click :guilabel:`Send to eTIMS` to send the vendor bill. When the
+   vendor bill has been confirmed on eTIMS, the **KRA invoice number** can be found in the
+   :guilabel:`eTIMS Details` tab.
+
+.. image:: kenya/purchase-order-lines.png
+   :alt: Bill registration steps.
+
+# Invoicing
+
+> **note**:
+>    The KRA does *not* accept sales if the product is not in stock.
+
+This is the **advised sales flow** in Odoo when selling:
+
+#. Create a **sales order**.
+#. :guilabel:`Validate` the delivery.
+#. :guilabel:`Confirm` the invoice.
+#. Click :guilabel:`Send and print`, and then enable :guilabel:`Send to eTIMS`.
+#. Click :guilabel:`Send & print` to send the invoice.
+
+Once the invoice has been sent and signed by the KRA, the following information can be found on
+it:
+
+- **KRA invoice number**;
+- Mandatory KRA invoice fields, such as **SCU information**, **date**, **SCU ID**, **receipt
+  number**, **item count**, **internal date**, and **receipt signature**;
+- The **KRA tax table**;
+- A unique **KRA QR code** for the signed invoice.
+
+# Imports
+
+Customs import codes are **automatically** fetched from the KRA eTIMS API servers every day. To
+fetch them manually, proceed as follows:
+
+#. Enable the :doc:`../../general/developer_mode`.
+#. Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for
+   :guilabel:`KE eTIMS: Receive Customs Imports from the OSCU`.
+#. Click the action in the list, then click :guilabel:`Run Manually` to fetch the codes.
+
+Go to :menuselection:`Accounting --> Vendors --> Customs Imports` to view the imported codes.
+
+The following steps are required to send and have **customs imports** signed by the KRA:
+
+#. Go to :menuselection:`Accounting --> Vendors --> Customs Imports`; The customs import is fetched
+   automatically from the KRA.
+#. Match the imported item with an existing registered product in the :guilabel:`Product` field (or
+   create a product if no related product exists).
+#. Set a vendor in the :guilabel:`Partner` field.
+#. Based on the partner, match the imported item with its related purchase order (see
+   :ref:`purchase steps <kenya/purchases>`). The stock must be correctly adjusted when the customs
+   import is approved.
+
+   If no related purchase order exists, create one and :guilabel:`Confirm` it. Then, confirm the
+   delivery by clicking :guilabel:`Receive Products`, then :guilabel:`Validate` on the purchase
+   order.
+
+#. Click :guilabel:`Match and Approve` or :guilabel:`Match and Reject`, depending on the
+   situation of the goods.
+
+> **note**:
+>    The JSON file received from the KRA is attached to the chatter of the customs import.
+
+# BOM
+
+The KRA requires all BOMs to be sent to them. To send BOMs to eTIMS, the product and its components
+*must* be :ref:`registered <kenya/product-registration>`. To access a product's BOM, click on the
+product and then click the :guilabel:`Bill of Materials` smart button.
+
+Make sure the :ref:`KRA's required fields <kenya/product-registration>` are filled in the
+:guilabel:`KRA eTIMS details` section of the :guilabel:`Accounting` tab in the product form, and
+click :guilabel:`Send to eTIMS`. The successful sending of the BOM is confirmed in the chatter,
+where you can also find the sent information in an attached JSON file.
+
+# Credit notes
+
+The KRA does not accept credit notes with quantities or prices higher than the initial invoice. When
+creating a credit note, a KRA reason must be indicated: In the credit note form, go to the
+:guilabel:`eTIMS Details` tab, select the :guilabel:`eTIMS Credit Note Reason`, and then select the
+invoice number in the :guilabel:`Reversal of` field.