eTims Configuration

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

Before starting the configuration, ensure that your organization has completed onboarding with Slade360 Advantage and that you have received valid authentication credentials for the target environment.

Accessing Navari KRA eTims Settings

To configure the integration, navigate to:

eTims → Navari KRA eTims Settings

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

Environment Configuration

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

• Sandbox: Used during implementation and testing
• Production: 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

The integration supports multi-company configuration within a single eTims Settings record, allowing one Slade 360 Advantage organization setup to manage multiple ERPNext companies under a unified compliance structure.

Each ERPNext Company is mapped to a Slade Cluster, and within that structure, each company can operate with its own Branches and Workstations as defined in Slade360 Advantage.

Only companies that are explicitly mapped within the settings are allowed to process and submit transactions to eTIMS. Unmapped companies will be blocked from compliance submission.

The Tax Payer’s PIN is automatically fetched from the Company Tax ID field and must match the KRA-registered PIN associated with the Slade 360 Advantage organization.

Data Scope Behavior

• Companies (Clusters): Each ERPNext company represents a Slade cluster
• Branches & Workstations: Managed under the Slade configuration per company
• Items & Customers: Shared across all companies under the same integration setup
• Transactions: Always company-specific and remain isolated per company

Accurate mapping is required to ensure proper validation, correct routing of transactions, and successful submission to KRA eTIMS.

API Authentication Configuration

Communication with Slade360 Advantage requires the following authentication credentials obtained during onboarding:

• Client ID → client_id
• Client Secret → client_secret
• Auth Username → auth_username
• Auth Password → auth_password

These credentials are used to authenticate and authorize all requests between ERPNext and Slade 360 Advantage. They must be stored securely and never shared publicly.

Submission Settings

The integration supports automated and manual submission modes for sales and stock transactions.

1. Auto Submission

• If enabled, transactions are automatically sent to eTIMS immediately upon submission in ERPNext.
• If disabled, transactions must be manually submitted using eTims Actions within the document.

2. Retry Frequency. Failed or pending submissions can be retried automatically based on the configured schedule either Hourly or Daily.

Item Classification Defaults

The Field Defaults section defines compliance values applied during item setup and transaction processing.

These defaults can be configured globally at settings level, inherited through Item Groups, or overridden at Item level.

Typical defaults include:

• Item Classification
• Taxation Type
• Country of Origin
• Packaging Unit
• Unit of Quantity
• Product Type
• Item Type

Proper configuration ensures that item data aligns with KRA eTIMS requirements and reduces validation errors during submission.