2.2 DigiTax Configuration

The eTims Settings DocType is used to configure Kenya Compliance via DigiTax before transactions can be submitted to KRA eTIMS through the OSCU integration framework. This setup connects ERPNext to DigiTax services and defines how compliance data is processed, submitted, and synchronized.

Before starting the configuration, ensure that your organization has completed onboarding with DigiTax and that you have received a valid API Key for the target environment.

Accessing eTims Settings

To configure the integration, navigate to:

eTims → eTims Settings

Create a new settings record or open an existing configuration. This page acts as the central setup point for communication between ERPNext, DigiTax, and KRA eTIMS.

Environment Configuration

Select the appropriate environment depending on whether you are testing or operating live.

The Sandbox environment should be used during implementation and testing, while the Production environment is used for live KRA submissions. Once configured, enable Is Active to allow the integration to process compliance operations.

The Server URL is preconfigured by default and normally does not require modification unless instructed during onboarding or support.

Company Setup

Select the ERPNext Company that will be used for compliance processing. The Tax Payer’s PIN is automatically fetched from the Company Tax ID field and should match the KRA-registered PIN associated with your DigiTax account.

Accurate company information is important to ensure successful validation and submission of transactions to eTIMS.

API Configuration

Communication with DigiTax services requires a valid API Key obtained from the DigiTax Portal during onboarding.

Under the Auth Details section, enter the API Key provided for your environment. This key is used to authenticate all requests between ERPNext and DigiTax services and should be kept secure.

Submission Settings

The integration supports automatic submission of sales and stock transactions to eTIMS. Submission frequencies can be configured based on operational requirements and how often ERPNext should synchronize notices and compliance information from DigiTax services.

A common setup is to use hourly refresh intervals together with automatic sales submission to support near real-time compliance processing.

Item Classification Defaults

The Field Defaults section is used to define the default compliance values applied during item setup and transaction processing. These defaults can be configured globally at the settings level, inherited through Item Groups, or overridden directly on individual Items where required.

Typical defaults include Item Classification, Taxation Type, Country of Origin, Packaging Unit, Unit of Quantity, Product Type, and Item Type