KNET Integration with Zoho Books in Kuwait, A 2026 Setup & Reconciliation Guide

Back to all articles

KNET is Kuwait's national payment gateway, practically every SME, restaurant, retailer and online merchant in Kuwait City, Hawalli or Salmiya collects through it. The problem: most Zoho Books users reconcile KNET settlements manually in Excel, costing 1,2 days every month. This guide walks Kuwaiti finance teams through a proper KNET ↔ Zoho Books integration, STK Push for invoices, MyFatoorah for online checkout, automated settlement reconciliation, and CBK-friendly audit trail.

Why KNET is the payments backbone in Kuwait

• Domestic dominance, over 90% of Kuwaiti card transactions ride on KNET rails (debit/POS, online, P2P).
• Bank-agnostic, every Kuwaiti bank routes via KNET; works with NBK, KFH, Burgan, Boubyan, Gulf Bank and CBK cards.
• Multi-channel, POS terminals, online checkout, mobile wallets, P2P transfers, government services.
• Settlement, KNET settles to the merchant's Kuwaiti bank account within 1,2 working days, typically net of fees.

Step 1, Which KNET integration mode is right for you

Three common ways Kuwaiti businesses connect KNET to Zoho Books:

• Direct KNET merchant integration, best for high-volume retailers; requires a bank merchant agreement and KNET technical setup; we build the connector in Zoho Creator + Deluge.
• MyFatoorah (most common for SMEs), a Kuwaiti payment-gateway aggregator on top of KNET; faster setup, supports KNET + Visa/Mastercard + Apple Pay; integrates natively with Zoho Books via API/webhooks.
• UPayments / Tap Payments, alternative aggregators with similar Zoho integration patterns.

Step 2, Connect MyFatoorah to Zoho Books

If you're going the MyFatoorah route (recommended for most SMEs):

1. In MyFatoorah → Settings → API Keys, generate a production API key.
2. In Zoho Books → Settings → Integrations → Custom Payment Gateways → MyFatoorah, paste the key.
3. Configure the supported payment methods (KNET, Visa, Mastercard, Apple Pay, Google Pay, Knet via STK Push).
4. Customise the invoice template to include a “Pay Now via KNET” button → the customer clicks → MyFatoorah hosted page → KNET → settlement.

Step 3, STK Push for invoice collection

For B2B invoices and recurring SME billing:

• Customer receives the Zoho Books invoice with the KNET pay link.
• The link triggers a hosted MyFatoorah / KNET payment page on the customer's phone.
• Once payment clears, MyFatoorah sends a webhook to Zoho Books → invoice auto-marked Paid → cash account credited → KNET settlement liability account debited.
• Net effect: zero manual entry. Your AR ageing reflects the payment in real time.

Step 4, Automated settlement reconciliation

This is the part that breaks most non-Shyphan setups. Three things have to match every settlement cycle:

1. KNET / MyFatoorah settlement report (CSV from the gateway portal), gross collection, fees, net settled.
2. Bank statement from your Kuwaiti bank, the net deposit hitting your operating account.
3. Zoho Books, invoices marked paid + the bank deposit transaction.

We build a Zoho Creator app that imports the daily KNET settlement CSV, matches it against bank-feed transactions in Zoho Books, and flags discrepancies. Finance team spends 10 minutes a week instead of 2 days a month.

Step 5, Recording KNET / payment gateway fees correctly

• KNET POS typically charges 0.5%,1.5% per transaction depending on volume.
• MyFatoorah charges around 1% + KWD 0.100 per KNET transaction; ~2.4% + KWD 0.100 for credit cards.
• In Zoho Books we set up a "Payment Gateway Fees" expense account and configure the integration to split each settlement: Invoice paid (gross) − fees (expense) = net cash received.
• Result: P&L shows true revenue + actual gateway cost; reconciliation is line-by-line, not summary-level.

Step 6, Refunds, chargebacks & disputes

• Refunds initiated in MyFatoorah / KNET get reflected in the daily settlement report.
• Zoho Creator app posts a Credit Note in Zoho Books with the gateway fee adjustment.
• Chargebacks (less common with KNET than international cards) go into a dispute queue with full evidence trail for the bank.
• FATCA / CRS-relevant transactions (high-value or cross-border) get auto-flagged for review.

Step 7, CBK reporting & audit trail

For licensed Kuwaiti companies (especially under the CBK Payment Services Regulation):

• Transaction-level audit log in Zoho, every state change tracked.
• AML transaction monitoring rules built in Zoho Creator, flag suspicious patterns (rapid multiple refunds, geo-mismatch).
• Monthly CBK return template generated from Zoho Analytics.
• Annual external auditor pack, settlement reports, reconciliation logs, dispute history exported in one click.

Common KNET,Zoho integration mistakes

• Recording gross instead of net, invoice shows paid at KWD 100 but only KWD 99 hit the bank; AR doesn't reconcile.
• No settlement-level matching, invoices are paid individually, settlement is batched; without matching logic, the bank account never reconciles.
• Manual fee entry, finance posts fees as a lump sum once a month instead of per-transaction; loses traceability.
• No refund handling, credit notes posted manually; never tied back to the original KNET transaction ID.
• Plain webhook without signature verification, security risk; we always verify the MyFatoorah/KNET webhook HMAC signature.

How a KNET,Zoho Books rollout looks for a Kuwaiti SME

1. Week 1, Discovery + KNET/MyFatoorah merchant account check + KWD chart of accounts review
2. Week 2, Zoho Books config, MyFatoorah API connection, invoice template with Pay Now button
3. Week 3, Zoho Creator settlement-reconciliation app build + bank-feed wiring
4. Week 4, Refund / chargeback workflow, fee account mapping, CBK return template
5. Week 5, UAT in production with real transactions, training, go-live

Typical cost in Kuwait: KWD 1,800, 4,500 depending on scope and CBK-licensed status.