ERPNext Accounting in Kenya

VAT templates and withholding in both directions

Kenyan VAT in ERPNext runs through tax templates on sales and purchases, item-level templates where a product is taxed differently, and party tax categories that pick the right template automatically. Which supplies are standard-rated, zero-rated or exempt is your advisor's decision; I build the templates to match and test each one against how they prepare the return.

Withholding is where Kenyan setups usually need more care, because it runs both ways:

• What you withhold. Professional, management, consultancy, rent or other payments your advisor places in scope can be handled through ERPNext's Tax Withholding Category, attached to suppliers and applied on purchase invoices or payments. A report of amounts withheld per supplier supports the returns and certificates.
• What customers withhold from you. Customers appointed as withholding VAT agents, and those deducting withholding income tax, pay you less than the invoice. In ERPNext the payment entry's deductions table posts the withheld portion to a receivable tax account, so the invoice closes in full.
• Certificates. A custom field on the payment records whether the customer's certificate has arrived, and a report lists those outstanding, so creditable amounts are claimed rather than forgotten.

Rates and categories change, so they are maintained as data your finance team can update, not code. The module overview is on ERPNext Accounting.

eTIMS as a ledger control, not only an integration

Kenyan businesses are expected to transmit tax invoices through KRA's eTIMS, and core ERPNext does not include that connection; it usually comes from a community app, an implementer's app or a custom integration. Picking and vetting that app is covered on my ERPNext Kenya page. Here the question is different: once invoices are flowing, how does finance prove that the ledger and KRA agree?

The controls I put in place:

• Response data on the invoice. The control number, signature or QR data returned by eTIMS stored in fields on the sales invoice and credit note, so the printed document and the ledger match.
• An exceptions report. Every submitted invoice without a successful eTIMS response appears on a list someone reviews daily, with a clear process for retries.
• Credit notes linked to originals. Returns and price adjustments reference the original invoice, so both the ledger and eTIMS show the correction.
• Item data. Classification and tax codes held on the item master and checked before an item can be sold.
• Monthly tie-out. Sales and output VAT in ERPNext compared with what KRA's records show for the same period.

Requirements on purchases, including how input VAT claims are supported, also matter; your advisor confirms what applies. Specifications change, so confirm current coverage of any app with Frappe or the implementer for your version.

M-Pesa Paybill and Till reconciliation at month end

Customers paying through M-Pesa create volume that bank-style reconciliation struggles with: many small receipts, references typed by customers, settlements to the bank in batches and transaction charges deducted along the way. Whether receipts reach ERPNext through a real-time app or a statement upload, the accounting design is what makes month-end close.

The structure I use:

• One clearing account per Paybill or Till, set up in ERPNext as a bank-type account, so receipts post there rather than straight to the bank.
• Statement imports from the M-Pesa portal into the Bank Reconciliation Tool, matching each line to a payment entry.
• Matching rules using the account reference, such as an invoice or customer number, with unmatched receipts parked in a suspense queue that a named person clears daily.
• Settlements to the bank recorded as internal transfers, matched on both the M-Pesa and bank statements.
• Charges posted to an expense account from the statement, not netted silently against sales.

At month end each clearing account should agree with the M-Pesa statement balance, and unmatched items should be few and explained. Payouts to suppliers or agents as business-to-customer transfers follow a similar clearing pattern with their own approvals. Related designs are on finance automation.

Shilling and dollar books and the auditor's year-end pack

Kenyan companies with foreign trade or funding may hold dollar accounts alongside shillings: exporters of tea, flowers or produce, importers settling suppliers abroad, NGOs and project-funded organizations receiving foreign grants. ERPNext keeps each company's books in shillings while letting bank accounts, customers and suppliers carry dollars or other currencies. Invoices store the rate used, and a month-end revaluation adjusts open foreign balances, separating unrealized from realized gains and losses. Your accountant decides the rate source; I make the routine repeatable.

The annual audit is where a well-designed ledger pays off. Kenyan companies typically report under IFRS or IFRS for SMEs, prepared by the accountant. From ERPNext I prepare:

• A trial balance mapped to the statement lines your accountant uses.
• Aged receivables and payables in both currencies, tied to the ledger.
• A fixed asset register with accounting depreciation, kept separate from any tax allowance schedule your advisor maintains.
• Bank and M-Pesa reconciliations for the year-end date.
• Withholding and VAT summaries that agree with filings.

Accounting periods are locked after sign-off so late postings cannot change reported figures. Groups with regional entities are covered on multi-company ERP and multi-currency ERP.

Upgrades, hosting choices and who owns the Kenyan apps

ERPNext carries no license fee because it is open source, but a Kenyan setup depends on code beyond the core: the eTIMS app, the M-Pesa app, local reports and print formats. Each ERPNext upgrade can break one of them, and a broken eTIMS connection stops compliant invoicing. That makes upgrade discipline an accounting control, not only an IT task.

The routine I write into the support agreement:

• All custom and local apps in version control, with core files left untouched.
• A staging site where every upgrade is tested with invoices, credit notes, M-Pesa receipts and the month-end reports before production moves.
• A named owner for each app, whether your developer, a Kenyan implementer or the app's maintainer, with response expectations written down.
• Rights to the source code of anything built for you, so you are not stranded if a provider leaves.

Hosting can be Frappe Cloud, a provider in Kenya or abroad, or your own server. Managed plans may limit which apps you can install, so list your apps first and confirm with Frappe or the partner. I sell no hosting or support. Wider context sits on the Kenya ERP consultant page and the Kenya hub. Sessions are remote, and the engagement runs in English.