Managing KRA Deadlines Across Multiple Clients
How Kenyan accounting practices track PAYE, VAT, and annual return deadlines across fifteen or more clients without missing one.
Every accountant in Kenya knows the three dates that matter. The 9th for PAYE, SHIF, and Housing Levy. The 20th for VAT. The 30th of June for annual returns. Multiply that by fifteen clients, and you have a calendar problem that most practices solve with a spreadsheet and a lot of memory.
The spreadsheet works until it doesn’t. Usually in a busy month, when two people are out sick and one client drops a surprise payroll addition on the 8th.
This is the workflow most practices end up with, and it is the one that fails least often.
The KRA calendar, precisely
Start with the actual deadlines. Most Kenyan accountants know these by heart, but writing them down prevents the annual scramble.
Monthly, by the 9th:
- PAYE return (P10) and payment
- SHIF contribution
- NSSF contribution
- Housing Levy
Monthly, by the 20th:
- VAT return (VAT3) and payment, for VAT-registered clients
- Note: the actual due date is the 20th of the following month, but the KRA portal accepts filings from the 1st. Most practices aim for the 15th as their internal target to leave buffer.
Annually, by 30 June:
- Individual income tax return (for sole traders)
- Company income tax return for companies with a December year-end (within six months of year-end, so 30 June for December companies)
Annually, by 31 December:
- Annual returns for companies with a June year-end
Quarterly:
- Not a KRA requirement, but if the client has provisional tax obligations, payments are due on the 20th day of the 4th and 10th months of their financial year.
Why practices miss deadlines
The failure modes are consistent. In the order of how often they happen:
The client’s data arrives late. The accountant knows the deadline. The client has not sent the bank statement. The reminder goes out. The client does not respond. The accountant is chasing on the 17th and the return goes in late.
The workload spikes and nothing is prioritised. Multiple clients due on the same day, and no clear order. The practice does the biggest client first because they are the loudest, and the smallest one slips.
One person is doing all the filing. When that person is out, nothing moves. No backup plan.
The tracking is in a spreadsheet nobody updates. The spreadsheet says the return was filed. It was not. The accountant remembers they were going to do it “after lunch.”
The three-part fix
The workflow that works has three components.
One: a single source of truth for deadlines. Not a personal calendar, not a spreadsheet that lives on one laptop. A single system where every client’s obligations are visible to everyone in the practice. When someone opens it, they see the whole picture, not just their own assignments.
Two: internal deadlines ahead of the KRA deadlines. The practice’s target is not the 9th. It is the 6th. VAT is not the 20th. It is the 15th. That gives three to five days of buffer for the inevitable late data, missing document, or filing error.
Three: defined roles for each client. One person owns each client’s filing. A second person reviews before it goes out. If the primary is out, the reviewer can complete it. No client has only one person who knows how to file for them.
The weekly rhythm
Practices that do not miss deadlines run a short weekly check. Fifteen minutes, every Monday morning. Three questions:
- Which clients have a deadline in the next 14 days?
- For each of those, is the client’s data in?
- If not, who is chasing it, and when?
Flag anything red. Anything that slips to the Thursday before the deadline is now a fire. Anything flagged on Monday has time to be handled calmly.
The client-side discipline
The practice cannot control the client’s timing, but it can set the rules.
Data deadline for clients. Every client contract should say: records must be received by the 5th of the following month for the practice to guarantee on-time filing. Clients who send data late accept the risk of a late filing penalty.
Automatic reminders. A reminder on the 1st, a follow-up on the 3rd if nothing has arrived, an escalation on the 6th. Scripted, not improvised.
A monthly data collection checklist. Clients who know exactly what to send (bank statement, M-Pesa statement, invoices, payroll additions) send it faster than clients who are asked vaguely for “your records.”
What causes penalties anyway
Even a disciplined practice occasionally triggers a KRA penalty. The ones that appear most often:
- Nil returns filed with visible activity. KRA cross-checks M-Pesa and bank. A nil return with visible income is a flag.
- Late VAT registration. The client crosses KES 5 million and the practice does not notice until the return.
- PAYE filed but not paid. The P10 goes in on time, the payment goes out the following week. Both trigger penalties.
Each of those is a case for tracking the client’s numbers against the thresholds, not just filing on schedule.
The realistic outcome
A practice running this discipline will not eliminate all risk. It will eliminate the deadline slips that come from the practice’s own process. Client-side late data will still happen. Threshold crossings will still occasionally surprise. But the 80 percent of missed deadlines that come from internal workflow problems go away.
That is the difference between a practice that grows from five to fifteen clients smoothly and one that starts missing filings at eight.
Related reading
Try Sentibooks free
Manage invoicing, expenses, payroll, VAT and full accounting in one place.
Start free trial