Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Market hub
KRA, eTIMS, M-Pesa and the Kenyan Shilling — the home market, and the one with the most statutory depth in the corpus.
Kenya charges VAT at 16% and files it monthly with the Kenya Revenue Authority by the 20th. Since the Finance Act 2023 phased out the legacy TIMS boxes, every VAT-registered business transmits invoices to eTIMS, which makes the invoice number and the tax point part of the compliance trail rather than an internal reference. Payroll adds PAYE, NHIF, NSSF and the Housing Levy on their own schedules, and M-Pesa paybill and till settlement is the default rail for both collections and supplier payments. These guides assume that stack.
Under eTIMS the document you issue has to reconcile to what was transmitted. Teams that number invoices per branch, or renumber after a credit note, discover the mismatch at filing rather than at issue.
A paybill statement records money arriving. It does not record which invoice it settled, and it cannot tell a customer deposit from a part payment. The matching step has to live somewhere, and a spreadsheet is where it usually goes wrong.
PAYE, NHIF, NSSF and the Housing Levy do not share a due date or a base. Running them off one monthly figure is the most common source of a penalty that only shows up months later.
These are the sales-tax presets AWRA OpsHub ships with, 1 of the 88 countries covered in total. They are headline national rates and a starting point for configuration — reduced, zero-rated and exempt categories still need setting up against your own chart of accounts, and rates change with each finance act.
| Market | Currency | Tax | Standard rate |
|---|---|---|---|
| Kenya | KES Kenyan Shilling | VAT | 16% |
Grouped by topic, newest first within each group.
Configuration takes a week. What takes ninety days is the organisation deciding which of its four stock figures is real, who is allowed to write off damage, and what replaces the WhatsApp group that currently approves purchases.
The instinct is to bring eight years across. That is how a clean system ends up full of dirty data. The three categories of record, only one of which travels, and the four hours of deduplication that decide whether your reports mean anything.
The figure you type on day one is what every future variance is measured against. Why the opening count has to be blind, what a proper count costs against copied figures, and how to value stock you are counting in.
Stock gets counted; the financial side has no equivalent. With no manual journal entry, an opening position arrives as real documents or not at all — plus why your chart of accounts has no numbers, and where the statutory book stays.
Six ways a rollout dies, ranked by how often we see them, and every one is organisational rather than technical. A missing feature has never been the cause — and the two that kill projects on their own are decided in a meeting, not bought.
Phasing is the safe answer and it is not free — you pay in a seam somebody carries by hand. Which modules genuinely cannot be separated, and the three situations where switching everything on at once is the better risk.
Two hours before go-live, permission design is politically free. Six months later it costs a week and makes enemies. How to build roles from the four separations that matter, against 255 permissions — and where the model stops.
A full day in a room three weeks early teaches almost nothing, and everyone involved knows it. Twenty minutes, one role, one task, at the moment of need — plus one uncomfortable rule about who should train the storekeeper.
Running both systems is correct for one module, for four weeks, with a stop date announced in advance. The weekly reconciliation that makes the double work worth it, and the one thing that destroys the test entirely.
Exit terms are the cleanest signal about how a vendor thinks, and you have most leverage over them before you join. The four questions, the answer almost no SME vendor gives well — attachments — and our own honest position.
Rollouts stall on small ambiguous decisions nobody has authority to settle. What the owner actually decides, the twelve to fifteen days it costs, why it should not be the IT person, and the six things to hand them in writing.
Go-live is the start of the work. The three numbers to record before you switch on, the four reports worth thirty minutes a week, why every threshold you configured is a guess until day 60, and the four signs it is genuinely being used.
Real numbers in shillings, ours included. What the subscription costs, what the first three months cost on top of it, and the three line items every quote leaves out because they are your hours rather than the vendor's.
The subscription is under a third of it. The five components, a five-year model for a forty-staff distributor, and the recurring item nobody puts in the spreadsheet — two hours a month of somebody tending the thing.
Real, predictable and absent from every proposal, because seven of the nine are your hours rather than the vendor's. Each with a rough shilling figure and the week it lands — plus three costs people budget for and rarely incur.
Whatever a vendor charges for, you will ration without deciding to. Per-user pricing pushes you into shared logins; per-module pricing breaks the records-referencing-records that made an integrated system worth buying. How to read either shape.
Four effects you can actually measure, how to get a before-figure for each, and the honest reason two of them are smaller than any vendor said. Including why one figure should be left deliberately blank.
A Nairobi build looks competitive against three years of subscription and never prices maintenance or the day the developer becomes unavailable. The four questions, a five-year comparison, and the two cases where building genuinely wins.
Free the way a puppy is free. Where the money actually goes, the three roles a self-hosted deployment quietly requires and nobody staffs, and the two situations where it is genuinely right in Kenya.
From a software company that would rather say it now than watch you cancel in month four. Includes the sizes where a spreadsheet is genuinely correct, and a plain list of the capabilities that would rule us out.
One page, five parts: four measured numbers, one deliberately blank, the full cost including your own hours, a paragraph on what you are not buying, and three numbers with a ninety-day review date.
A dollar-priced subscription is an unhedged monthly currency position renewed forever. What a 20% move does to it, the three second-order costs nobody quotes, and the difference between a contract currency and a display currency.
Overstock has an invoice; a stockout has no document at all. Which is exactly why every business carries too much of the first and cannot tell you what the second costs. The four layers of a stockout, and where the two curves cross.
Six routine tasks with a stopwatch against them and an annual figure each. The largest line is the one nobody complains about — and three of the six do not improve at all, which is the part that makes a case survive review.
Every integrations page is a grid of logos, and the tiles are four completely different products with four different failure modes. How to decode any of them with two questions, and which one to connect on day one.
Thirteen templates download and eight import. Which is which, why the other five deliberately have no importer, the dependency order that stops a file failing on row one, and the fifty-row habit that substitutes for a preview.
There is a real API and there is no developer portal. How tokens are issued, why a token carries the user's permissions rather than its own, what the API is genuinely good for — and why continuous two-way sync is not a shape it supports.
The feature that removes a daily job: a C2B payment quoting an invoice number attaches itself to that invoice. Collections, disbursements and reversal on your own Daraja credentials — plus the four gaps to plan a payout process around.
Two independent guards against double filing, retries with backoff, the signed receipt stored on the invoice — and the two gaps a VAT-registered business must decide about before go-live: credit notes, and what a till does offline.
"Sync" does more work on integrations pages than any other word in software marketing. Ours pushes vendors, items and purchase orders out on a button and reads nothing back — including a note on where our own connector copy overstates it.
In Kenya an alert not on WhatsApp or SMS has not arrived. Both work on your own credentials, WhatsApp has one template rule that catches everybody, and the volume discipline matters more than the setup — because muting is silent and permanent.
The cheapest integration available and the only one that changes behaviour rather than moving data. Six channels, why three topic channels beat one, and the mute problem that makes this look like it is working for months after it stopped.
Three different things get sold as offline and only one is worth anything to a driver in Kitui. Idempotent replay so a lost response cannot duplicate work, conflicts surfaced rather than resolved, and device trust that expires.
The list vendors do not publish. Bank feeds, other mobile money rails, other tax authorities, other accounting packages, inbound messaging of any kind, marketplaces and scheduled pulls — with the reason for each and what to do instead.
The hardest inventory problem in Kenya, and not because of volume — the same alternator carries four names, so stock is counted three times and one person holds the mapping. What fixes it, in what order, and the vehicle record this does not have.
There is no work order here, so a job card is a project — which gives you parts at stamped cost, labour hours and a real margin per job. What it does not give you is a vehicle history, and that gap is the one to weigh.
"Will this fit a 2014 Probox" is a database query executed by a man who has done it for eleven years. Why fitment is a licensed data product rather than a feature, what searchable fields genuinely buy you, and when to run a catalogue alongside.
A 38% landed uplift turns a 30% markup into a loss, and that is the ordinary imported container rather than a bad one. Three customers at three prices, and the supplier-price-list gap that means nobody checks an invoice against an agreed rate.
Most workshops make their money on parts and believe they make it on labour — and the two answers recommend opposite investments. How to get an overhead-per-hour figure, and what to charge when a customer brings their own parts.
An internal workshop has nobody querying the bill, which is why fleet stores leak more than commercial ones. Cost per vehicle without a vehicle record, tool custody that works, and the honest position on service scheduling.
The one place serial tracking pays back in the first month. Read the serial and you know when it sold, who supplied it and whether the claim is live — and six failures from one purchase order becomes a claim against your supplier.
Thirty vehicles, each individually costed, individually aging, each carrying unfinished paperwork. Item-per-vehicle is the model that works — and if credit is how you actually sell, this covers the yard and not the business.
A mixed container is the exact case where allocation matters most and the correct basis is unavailable. Why quantity allocation destroys a clip's cost, the split-delivery defect to work around, and why demurrage always lands after you start selling.
Customers return because you know their car, and that knowledge lives in a folder that gets lost and a mechanic who leaves. How far a registration-prefix convention gets you, and the declined-work note that is worth more than any discount.
The gap between recording stock and being told what to buy, when, and from whom is the difference between digital and intelligent. What smart inventory and intelligent procurement mean in 2026 — and how to choose a system that delivers both for a Kenyan operation.
Most ERP regret comes from buying the wrong size, not the wrong brand. A buyer's guide that starts from your operation, right-sizes the system, and gets you there without overbuying.
Every business runs on a rhythm of statutory deadlines, and missing them costs penalties. The recurring compliance calendar in plain terms — and how to let your system carry it.
An open-source ERP can do the job — the real question is who makes it do the job and keeps it running. An honest comparison on total cost, implementation, developer dependency, and eTIMS/M-Pesa compliance.
Excel is free the way a leaking pipe is free — reconciliation labor, error rates, the one-person dependency, and stale-data decisions, computed honestly.
ERP projects fail in predictable places — dirty master data, big-bang go-lives, demo-data training. The five-phase checklist from decision to retired spreadsheets.
eTIMS mandates, M-Pesa-native operations, multi-branch growth — the forces pulling Kenyan SMEs off spreadsheets, and how the successful ones sequence the move.
License models, the implementation costs nobody quotes upfront, honest three-year totals in KES, and the questions that expose hidden pricing.
Ten questions that separate partners who will still serve you in year three from vendors who disappear after the deposit — references, SLAs, compliance, and exit terms.
What each Kenyan compliance regime actually requires from your system — eTIMS invoicing, statutory payroll, withholding, records — plus vendor test questions.
You do not need to be a data business to be a data controller — an employer with payroll already is. Where personal data actually hides, what retention means in software, and the honest limit of any product. Not legal advice.
Four of the Act's seven operational duties are wholly yours, three are shared, and none can be discharged by a purchase. The controller and processor boundary, what belongs in a processing agreement, and the breach-notification gap stated plainly.
Kenyan businesses make everyone an administrator in the first two weeks because it stops the complaints — and deletes the meaning of every other control. Getting back to least privilege without blocking work.
An auditor picks one line and asks you to rebuild it. The documents, the approvals and the change history together — plus the retention trap that makes evidence expire before the obligation does.
Ghost suppliers, inflated prices, adjustments that cover a count, ghost employees, and the till. Each needs two capabilities in one pair of hands — and each has an aggregate view that exposes it in ten minutes.
One login per location is the most common security arrangement in Kenyan SMEs, and it turns your system from a record of what people did into a record of what a place did. Fixing identity first.
Every term you want at the end of a vendor relationship is available before signature and none of it afterwards. No-cost export, post-termination destruction, the grace period on deletion — and where the disposal boundary actually falls.
What NGO teams should look for in an ERP — donor fund segregation, procurement governance, asset registers, and Kenya-specific compliance — with a practical evaluation checklist.
A practical system for tracking restricted funds from grant agreement to donor report — fund segregation, budget lines, burn rates, and audit-ready advances.
The seven procurement problems behind most NGO audit findings — emergency purchases, quotation theatre, undocumented approvals — and the fixes that hold up in the field.
A complete, adaptable procurement policy for Kenyan NGOs — thresholds, committees, conflict-of-interest rules, and emergency procedures you can copy into your manual.
The audits Kenyan NGOs face, the findings that repeat across the sector, and a 90-day plan that turns audit week from reconstruction into retrieval.
The statutory stack done right, plus the NGO layer: allocating staff costs to grants, paying casuals and enumerators properly, and the monthly reconciliation triangle.
The advance lifecycle, per-diem rules that stop field drama, and M-Pesa discipline — closing the gap between when money moves and when evidence is captured.
A till that sells and a stock system updated later will disagree by Friday. The warehouse behind each counter, the batch that leaves with the sale, and why the system should refuse a sale it cannot supply.
Four decisions hide inside every return, and collapsing them into one hurried moment is what breaks the records. Why restocking must be deliberate, how exchanges are really two transactions, and how unrecorded refunds manufacture till shortages.
The smallest document in your business and the one customers most often need. What belongs on the slip, why a stored copy settles disputes paper cannot, and the practical realities of digital receipts in Kenya.
The end-of-shift count is where most Kenyan retail disputes happen, and almost all of them are arithmetic nobody wrote down. The float, the drops, the expected figure and the variance.
eTIMS is the one fiscal regime on this blog we integrate with rather than reconcile against. What changes at the counter, what happens to returns, and what to confirm with KRA.
A till that stops working when the connection drops teaches your cashiers to keep a paper book — and then you are running two systems. What offline selling requires, and what to decide before it happens.
Overtime is the payroll line nobody can defend and everybody pays. Why derived overtime beats claimed overtime, where the approval step earns its keep, and why we state no multiplier anywhere.
Exits run on goodwill and a cake, and the risky parts get done later by whoever remembers. The four workstreams, why you reassign before you revoke, and the logins no offboarding process ever touches.
Most Kenyan employers do not have an HR problem — they have an HR records problem that only becomes visible on payroll day. What to fix in what order, and the straight answer on what is automated and what is not.
Four statutory deductions, four sets of rules, and rates that move. What a Kenyan payroll run should do, why date-effective rules matter more than the arithmetic, and the reconciliation that catches errors before the money leaves.
Leave is the first thing employees dispute and attendance is the first thing that quietly corrupts payroll. Both are the same problem: a record that either exists when it happened, or gets reconstructed later from memory.
The employee file is the least glamorous thing in HR and the first thing anyone asks for — in a dispute, at an audit, or when the person who knew everything about your staff resigns.
Most project plans are tasks with dates typed beside them, which is a wish rather than a schedule. What dependencies buy you, why slack decides which delays matter, and the procurement lead time nobody records.
Projects end twice — when the work stops, and months later when the last invoice and the last claim land. Why the reported margin is never the real one, the retention trap, and the one review table that changes future bids.
Most organizations can tell you what a project was supposed to cost and what it eventually cost. The expensive gap is the middle — the months where an overrun was forming and nobody could see it yet.
An overrun is not an event, it is a trend that becomes an event. The reporting rhythm and the three numbers — budget, committed, actual — that let you see one forming in time to do something.
For a firm that sells expertise, time is the only inventory — and the one form of stock that vanishes if you do not count it the same day. Utilisation, realisation, and where the hours actually disappear.
A cost that lands nowhere lands in overhead — and overhead is where project profitability goes to hide. The four routes cost reaches a job, and the one-field rule that closes all of them.
A ticket at the wrong desk teaches people the system is slower than walking over. Why the category carries the policy, why priority does not move the clock, and what escalation means when nothing pages anyone.
Tickets received and closed are the two most reported and least useful numbers in support. The four measures that show whether a desk is coping, why reopens beat resolutions, and how to read satisfaction honestly.
Support runs on email and WhatsApp until the day something important is lost, and then everybody agrees it should have been on a system months ago. The threshold, what a helpdesk must do, and where ours stops.
An SLA you cannot measure is a hope you have shared with a customer. What response and resolution targets require, why the pause makes them fair, and how to set targets you will not quietly abandon.
The largest pile of untracked work in most Kenyan organizations is not customer support — it is colleagues asking colleagues for things. Why internal requests are the best place to start.
Most support portals fail because they ask people to create an account before they can complain. What makes an intake channel people actually use, and the honest limits of a portal.
Most board packs are assembled by hand in the four days before the meeting. What belongs in one, why a certified definition beats four accurate spreadsheets, and the four choices that make two reports disagree.
A shared report is a permission decision wearing a friendly interface. Roles versus named people, the difference between sensitive and export-restricted fields, and why row-level filtering is one report per audience.
Every business asks for reporting and most end up with reports nobody opens. The difference between a report and a decision, and why reporting problems are nearly always records problems in disguise.
A dashboard with twenty tiles is a wall decoration. How to choose the six numbers that would have warned you about last year's surprises, and the rule that keeps a dashboard useful.
The gap between a report that exists and one that reaches the person who acts on it is most of the value. Scheduling, who to send to, and how to stop scheduled reports becoming ignored mail.
The most expensive report is the one somebody assembles by hand every month because asking IT takes three weeks. What a report builder removes, and how to avoid the mess when everyone can build one.
Nobody decides to become a lender; it happens one favour at a time. Why exposure matters more than the invoice at the counter, how to set limits from behaviour, and the collection rhythm most retailers waive for their biggest customer.
Retail margin is won at the buying desk and lost in the details nobody records. The four things you agreed, the check that pays for itself, and why longer terms can beat a lower price.
eTIMS on every receipt, offline resilience, shrinkage visibility, and multi-branch control — what to demand from a retail system, with an evaluation checklist.
Shrinkage is five problems, not one — theft, miscounts, damage, short-delivery, and paper sales — and each hides in a different gap. Close them all.
The second branch is where trust stops being a control system — live dashboards, governed transfers, and branch P&Ls that keep growth profitable.
The 20-minute evening routine that keeps a shop honest — cash, M-Pesa, and card reconciled against the system, shift by shift, variances named.
Linen is the stock nobody counts because none of it is expensive, and one of the largest recurring purchases in the building. Par levels, the quarterly circulating count, and amenities as a cost per occupied room night.
Functions look like the most profitable business a hotel takes, until somebody costs one. Why an event is a project rather than a sale, the three numbers to fix before the day, and what costing six events tells you about which to chase.
Perishable stock, un-weighable portions, thin margins — store-to-kitchen flow, food cost decomposition, and the daily counts that decide the month.
The menu is a price list for recipes nobody costed — live recipe cards, portion discipline, waste as a transaction, and the four-box menu grid.
Three supply chains in one apron — contracted dry goods, daily fresh buying with price-survey bands, and protein weighed twice. Each leaks differently.
The kitchen loses money in percentages; the bar loses it in bottles. Nightly bottle math, pour discipline, empties fraud, and variance by shift.
A budget approved in January and consulted in November is a forecast that was overtaken. Vote heads as controls with owners, why committed spend is the number that matters, and budgeting by term rather than by thirds.
Buses are the most expensive assets most schools own and the least documented. Why the odometer reading at the pump is the whole fuel control, what a trip log should leave behind, and whether the transport fee covers the service.
Schools are three businesses in one uniform — fees, logistics, and assets. What operations software must handle, and where school money actually leaks.
Term dates are known years ahead — yet week one is always a buying emergency. The term procurement cycle, the big four contracts, and kitchen arithmetic.
One invoice per student, a unique payment reference, all channels into one ledger — how bursars end the evening matching game and make arrears report themselves.
Schools budget annually for equipment they already own. Custodians by name, term verification rhythms, and maintenance that beats breakdown.
For a small part of a clinic store the question is never "how many" but "who, when and on whose authority". Where to spend two-person discipline, why small discrepancies get investigated here, and what a general inventory system cannot discharge.
A clinic can be busy, well-run and quietly losing money on half of what it does. Building a consumable cost per service in an afternoon, and why waste concentrates in your least-used service rather than your busiest.
A stockout is a clinical event and expired stock is money in the disposal drum — batch tracking, FEFO, consumables par levels, and the weekly hour that runs it all.
Expiry routinely eats 3–8% of drug spend invisibly. Where it comes from, the 30/60/90 routine, and the purchasing habits that stop it at the source.
Broken equipment announces itself; miscalibrated equipment misdiagnoses quietly. Three maintenance tiers, calibration discipline, and the replacement horizon.
Reorder points from consumption, shelf-life terms in writing, supplier performance tracked — the upstream half of facility stock control.
The largest cost category on most projects has the weakest evidence behind it. Valuing work instead of processing a claim, comparing issued materials against valued progress, and mirroring retention on both sides of the chain.
Variations are lost in small pieces, agreed on site under pressure and argued about at final account. Why the instruction matters more than the price, the five-line note that survives, and why coded costs settle higher than estimates.
A contractor runs three businesses at once — materials, plant, and fixed-price promises. Where the money leaks on a Kenyan site, and how the profitable ones keep all three under control.
Materials are the biggest job cost and the easiest to lose — not dramatic theft, a hundred small unmeasured gaps. Close them by measuring flow, not suspecting people.
The BQ is a promise made at tender; the site is where it meets reality. Track budget, committed, and actual against every line — while there is still a job left to correct.
A contractor's plant is capital designed to move — which is why it goes idle, goes missing, and breaks down unplanned. Custody, movement history, and service discipline.
A recharge recovering 88% of a bulk bill loses money every month, invisibly. The recovery ratio per building, why you record readings rather than consumption, and the handover reading that ends a whole category of dispute.
A lease that expires unnoticed costs more than a month of rent — it costs the negotiation you never had. Four dates per lease, what a turnover truly costs, and why the renewal conversation belongs at ninety days.
A managing agent is trusted with other people's buildings and other people's money. The four disciplines — collection, maintenance, trust funds, and owner reporting — that keep both in good order.
Collection is the heartbeat of an agency and where most bleed time. The cycle that ends the monthly matching game, ages arrears into a managed list, and reconciles every channel.
Maintenance is where agencies lose money and trust at once — through repairs nobody tracked, approved, or verified. A work-order discipline from report to verified-closed.
Most money flowing through an agency is not the agency's to spend. Keeping deposits, landlord funds, and agency income provably separate is the discipline that prevents disaster.
The questions that cause trouble at a SACCO AGM are almost never about the loan book. Preparing the four predictable ones with evidence created during the year, and why a depreciation schedule cannot answer where the vehicle is.
The largest controllable expense, paid from members' money, discussed in front of the members. Date-effective statutory rules, allowances that need a record made before payment, and presenting a wage bill as four drivers rather than one total.
The core system runs the loans; nothing runs the rest. Procurement, assets, branch expenses, and payroll — where member money leaks and governance is tested.
The AGM question is never subtle: who supplied, at what price, who else quoted? Thresholds, conflict-of-interest discipline, and files that answer for themselves.
The auditor's schedule says what was bought; nothing says where it is. Fleets, branch fit-outs, ICT custody, repossessed collateral, and the register that survives elections.
Every operating shilling is a dividend shilling that left early — live budget envelopes, sitting allowances done properly, and the monthly five-number review.
Retainers look like the most stable revenue a firm has and are often its least profitable work. Why you record time on fixed fees especially, the three billing models and their disciplines, and the final milestone nobody defines.
The hardest question in a professional firm, usually answered by asking around. Capacity as a number rather than an impression, why utilisation targets create the wrong behaviour, and the weekly meeting that beats any tool under fifty people.
Law, audit, and consulting firms sell time — but still run on operations they never systematize: which engagements make money, whether client funds are separate, and where the firm's money goes.
Utilization tells you how busy your people are; profitability tells you whether it was worth it. In a firm that sells time, confusing them is how a fully-booked practice loses money.
Money a firm holds for clients is not the firm's money, and proving that at any moment is a professional obligation. What proper segregation of client and trust funds actually requires.
A firm with no cost of goods leaks money through overhead — subscriptions nobody reviews, disbursements never recovered, buying nobody approved. How to close the gaps without making finance the enemy.
Buyers increasingly ask which farmer, which day, which lot — and confine aggregators who cannot answer to the spot market. Choosing what a lot is, why backward traceability is the hard direction, and the distance between a record and a certification.
A cooperative tractor is a member service, a revenue line and an asset quietly consuming the society's surplus. Costing an hour honestly, the hire log that replaces an hours meter, and presenting the subsidy members never voted for.
A co-op sits between hundreds of farmers and a demanding market, and its value is trust — fair weighing and grading, correct on-time payments, and money that survives the journey. The disciplines that keep it.
The moment produce hits the scale is when a co-op earns or loses trust. Weighing, grading, and paying fairly — and proving it — is the core of the cooperative promise.
Advancing seed and fertiliser on credit grows farmers — and quietly loses money when it is tracked as neither stock nor debt. How to run check-off without the leak.
A shocking share of Kenyan produce is lost between farm and buyer, invisible because nobody measures where. Turning loss into a number at each step protects the margin.
The most sensitive data a church holds and the most useful. Deciding which giving is attributed and who may see it, why pledge totals are the wrong planning figure, and the annual statement that makes the record trustworthy.
A second congregation creates an accounting problem before it creates a ministry one. The three models, why income must be recorded gross at the site, and the remittance reporting that keeps branches from resenting the centre.
A church runs on the trust of those who give to it — and trust in money matters is built by controls, not intentions. How well-run churches handle offerings, project funds, buying, and assets.
When members give toward a building, the money carries a promise. Pledges against receipts, restricted from general funds, spent transparently — how the promise is kept to completion.
Churches buy constantly and own more than they realize — yet do both on trust and memory. Governing the spending and registering the assets is stewardship the members are entitled to expect.
The delivery note that comes back illegible is why an invoice gets disputed six weeks later. Why a printed name beats a signature, how to express a partial delivery, and treating delivery paperwork as a receivables control.
The return trip costs more than the margin on the original job. Why two of the five causes are intake failures, treating each van as a counted stock location, and the parts you fit but never bill.
For installers, distributors, and service crews the office is wherever the van stopped — job evidence, traveling stock, custody, and fleet discipline in one guide.
Cost per vehicle, fuel-to-distance baselines that beat gadgets, service on schedule, and the route math that decides which vans deserve to exist.
Manufacturers price from a bill of materials and lose money on the difference between the recipe and the run. Where yield, landed cost and rework belong, why contribution beats full cost for pricing, and the quarterly re-derivation that keeps a price list honest.
"I bought 3 tonnes of maize and sold flour — did I make money?" Recipe control, yields, landed costs, and quality holds for Kenyan processors.
Freight, duty, clearing, transport, and currency all belong in the unit cost — or your margins are fiction and your best-sellers may be priced below cost.
The batch loop — plan, issue, produce, receive, reconcile — and the two numbers per batch that separate measured processors from hopeful ones.
A sale is not finished when the customer says yes. It is finished when the money is banked, the stock has moved, and the invoice matches what was actually delivered — and the gaps between are where revenue evaporates.
Kenyan businesses lose far more to slow payment than to bad debt, and chasing harder is rarely the fix. Most late payment is friction you created at invoicing — plus the escalation ladder for when it is genuine.
Margin is rarely lost in one bad negotiation. It is given away in a hundred small concessions nobody recorded, by people trying to close a sale — which is why the fix is structural rather than motivational.
The cheapest sale a business can make is the second one to a customer it already has — and the reason most do not make it is that the record of the first sale lives in a salesperson's phone.
Most Kenyan businesses do not need better accounting software. They need accounting to stop being a separate system that operations reports into weeks later — because that gap is where every number becomes negotiable.
Profitable businesses run out of money regularly, and almost always with two weeks of warning nobody was looking at. A thirteen-week rolling forecast you can maintain, built from records you already have.
Nobody ever went bust on expense claims, which is why they go unmanaged for years. The four structural gaps that make ordinary behaviour expensive, and the approval design that closes them.
Year-end is only painful when treated as an event instead of a consequence. The practical close checklist for a Kenyan SME — and how to make next year's close a formality.
The generator that failed had been serviced twice in four years and nobody could say when. Maintenance as a recorded movement, the rising-frequency pattern that decides repair versus replace, and why there is no scheduler.
Getting an asset onto the register is the easy half. Five ways assets leave, why scrapping needs its evidence created before the item is gone, and the rule that keeps a register credible: retire, never delete.
Most Kenyan organizations have an asset register that was accurate the day it was typed. What makes one stay true — named custody, recorded movement, a verification rhythm — and the honest limits of a register.
Each of these sets out what is built today and what is still on the roadmap for that market.
Help Center
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.