Zoho Analytics Consultant in Kenya

Seeing M-Pesa and bank collections clearly

For a Kenyan company collecting through mobile money and banks, the ledger tells you what has been matched to invoices. It is much worse at telling you what is sitting unmatched, which channel is growing, or which customers routinely pay without a usable reference. Those questions drive cash flow and credit decisions.

In Zoho Analytics I build a collections model from:

• Paybill and till statements imported on a schedule, or through an integration where one is in place and tested.
• Bank statements or feeds for shilling and dollar accounts.
• Customer payments as recorded in Zoho Books or your accounting system.

The dashboards then show:

• Receipts by channel, branch and day, compared with the same period before.
• Unmatched receipts aged by how long they have waited, with the payer's phone number masked for users who do not need it.
• Customers whose payments regularly arrive without a recognizable reference, so sales can correct the habit.
• Collections against invoices due, as an early view of the month's cash.

The matching itself is done in the ledger, under the process your finance team owns. Analytics shows how well that process is keeping up, so a backlog is noticed in days rather than at month-end.

Grant budgets, burn rates and donor views for NGOs

Kenyan NGOs and program implementers report to donors on spending against approved budgets, often in the donor's currency and format. The accounting system holds the transactions, but program managers need a faster view: how much of each budget line has been used, what is committed, and whether spending is on pace for the grant period.

What I build, with your grants and finance teams:

• Budget tables for each grant by budget line and period, loaded from the approved budget and revised when the donor approves changes.
• Actuals from ledger entries coded with grant and budget line, so the dashboard and the books agree.
• Commitments from approved purchase orders where your system records them.
• Burn rate views by grant and line, highlighting underspend and overspend against plan, in shillings and the donor's currency.
• Activity progress joined from Zoho Projects where activities are tracked there, so spending can be read next to delivery.

This is a management view. Donor financial reports, allowable cost decisions and audit schedules remain the responsibility of finance, prepared from the ledger. If grant codes are missing or inconsistent in the ledger, Analytics will expose the gaps but cannot fill them; coding discipline comes first.

Shillings, dollars and East African entities

Many Kenyan companies trade in both shillings and dollars, and regional groups add entities in Uganda, Tanzania or Rwanda with their own currencies and ledgers. Parents abroad and donors may want results in dollars or euros. Mixing these without a clear method produces numbers nobody can defend.

The model I set up:

• One rate table holding the rates your accountant chooses, whether booked, average or closing, rather than rates typed into individual reports.
• Local currency first: each entity's figures are kept in its own currency, with converted views clearly labeled.
• An account mapping so every subsidiary's ledger codes roll up to shared reporting lines that group finance looks after.
• Intercompany flags, so management fees and stock transfers between group companies are excluded from combined totals.
• Row-level access so country managers see their own entity and group finance sees all.

Legal group accounts, with eliminations and an audit trail, are produced by finance in the books or a dedicated consolidation product. Zoho Analytics gives management a timely, consistent view. Whether each regional entity runs its own Zoho Books organization or another package is a structural decision discussed on the Zoho in Kenya page; the reporting model can work with either.

Non-Zoho sources, data protection and plan limits

Kenyan businesses rarely run everything on Zoho. Common sources include other accounting packages, an ERP at the parent, a distribution or route sales app, a point-of-sale system, and many spreadsheets. Each needs a defined feed:

• Native connectors where Zoho supports the source, checked against your edition.
• Scheduled file imports from cloud folders where only exports are available, with a fixed layout and an owner.
• A database bridge for systems on local servers, where Zoho supports the database type, hosted on a machine that stays on.

Personal data needs care. Under Kenyan data protection law, customer phone numbers from mobile money statements, employee details from payroll exports and beneficiary information in NGO data are personal data, and some is sensitive. I bring in only what reports require, mask phone numbers where full numbers are not needed, apply row-level access by entity or program, and review shared links before they are enabled. I get written confirmation from Zoho of the data center behind the account and file it, together with donor clauses about where program data may sit, for your data protection officer.

Row, user and refresh limits depend on your plan. So before loading several years of history, I ask Zoho, or whoever administers your licenses, what your tier allows.

What Zoho Analytics cannot fix for a Kenyan organization

Analytics is a mirror. It reflects the quality of your processes and data back at you, faster. Before starting, be honest about these:

• Unmatched receipts. If customer payments are not matched in the ledger, dashboards will show a growing pile, not a solution. The receipt process needs fixing in finance.
• Uncoded transactions. Grant burn and branch margin depend on grant, project and branch codes being applied consistently at entry.
• Tax and statutory reporting. eTIMS submissions, VAT and income tax returns and audited accounts are prepared in the books by your accountant; dashboards play no part.
• Late month-ends. A ledger that closes weeks late means dashboards show old news. My business process consulting in Kenya page covers fixing the close.
• An existing BI standard. If the parent or a major donor already requires another reporting platform, a second tool may create competing numbers.

No vendor pays me, I resell no licenses and take no commission, so I can recommend a smaller scope or a different tool, such as Power BI, when it fits better. Sessions run remotely during Kenyan office hours. See the Kenyan ERP advisory page and the Kenya overview for the wider systems picture.