Deni Book Killer
PipelineA lead magnet and service funnel for bookkeeping rescue, tax cleanup, and year-end recovery.
- Offer-based landing pages
- Lead capture workflows
- Local trust messaging
SokoDispatch is an M-Pesa to KRA eTIMS auto-accounting SaaS for Kenyan businesses. It connects shop payments to compliant invoices, QR-ready receipts, and WhatsApp or SMS delivery in seconds.
Live preview · Transactions update when you simulate a payment.
| Receipt | Customer | eTIMS | Amount |
|---|---|---|---|
Connect your account Sign in to view your M-Pesa transactions and linked shop data. | |||
Your linked shops and accountant access will appear here once the verified account is loaded.
Revenue snapshots and invoice momentum help you decide what deserves attention before the end of the day.
All affiliate data is linked to the same verified-user flow used for shops and accountants.
Plan blog topics, keywords and publishable material before the channel goes live.
Keep routine operations visible without leaving the core business dashboard.
Record customer debt, follow due dates and settle rows when the balance is paid.
These modules build on the same verified-user and business-management foundation already in place.
A lead magnet and service funnel for bookkeeping rescue, tax cleanup, and year-end recovery.
Operational automation for payroll, staff reminders, and compliance checklists tied to each business record.
A revenue-visibility engine that highlights margins, late collections, and decision-ready business snapshots.
Switch plans as your shop or client list grows.
For one busy shop
For growing daily sales
For high-volume shops
No. Till and Paybill payments go directly to your Safaricom account. SokoDispatch records the callback and creates the related eTIMS invoice.
Personal-number support is planned through the SokoDispatch Lite Android app, which reads payment confirmation SMS with your permission. A Till or Paybill connection is recommended when available.
This build uses a clearly marked mock invoice until KRA OSMS sandbox credentials are configured. The transaction path and invoice status are already wired for that integration.
The callback saves the M-Pesa transaction first. With Redis configured, invoice creation runs in a retrying background queue; failed invoices stay visible for follow-up.