High Court rules internal bank maker-checker trails do not prove payment

On July 2, 2026, High Court Judge Justice Benard Murunga delivered a judgment in Consolidated Bank Ltd v Muteithia Kibira Advocates LLP (Civil Appeal E323 of 2025, [2026] KEHC 9415 (KLR)) that underscores the strict evidentiary standards required to prove electronic payments in commercial disputes. The ruling reinforces a fundamental legal principle: internal banking workflows, including maker-checker approvals and payment schedules, are legally insufficient to prove that a transaction was completed. The High Court clarified that financial institutions and corporate litigants must provide verifiable evidence that funds were actually delivered to the recipient's account rather than simply pointing to internal administrative log histories.

The Background of the Dispute

The legal battle traces back to a 2017 billing conflict over professional legal services. Consolidated Bank claimed it had deposited a Sh72,460 installment toward a Sh497,102 fee note issued by the law firm defending it in an employment lawsuit. The advocates maintained that the deposit never hit their accounts.

To defend its position, the bank produced an internally approved Deposit Request Note alongside its internal payment schedule. Justice Murunga dismissed the bank's appeal and upheld the Small Claims Court’s original award for the full fee balance. The court clarified that internal administrative milestones are merely an approval workflow, not absolute proof of funds delivery.

Why Internal Logs Fail as Evidence

The decision exposes a practical vulnerability in routine corporate accounting and dispute resolution. Many corporate legal teams operate under the assumption that an internal database debit or a stamped approval slip acts as a definitive liability shield.

By distinguishing between an authorization trail and an actual transfer, the High Court has clarified the burden of verification. If an organization claims it sent money, it must produce external electronic funds transfer (EFT) records or valid remittance advice. The new baseline requires a verified settlement confirmation generated directly by the receiving institution's ledger. Operating inside an isolated database registry is no longer enough to settle a payment dispute.

Analytical Extension to FinTech and Mobile Money

While this specific case centered on a professional services fee note, the underlying legal logic creates immediate legal exposure if applied to East Africa’s wider digital commerce ecosystem.

Consider how this applies to integrated payment channels linking commercial banks directly to mobile money systems. Automated bank-to-wallet platforms handle high transaction volumes daily, where network timeouts and ledger mismatches are frequently cited as operational bottlenecks for local merchants.

If courts apply Justice Murunga’s logic to everyday merchant settlement disputes, a simple confirmation message or internal system debit will fail to protect a platform. Digital payment providers would face an immediate mandate to verify end-to-end delivery, confirming the funds actually cleared into the receiving account.

Technical Overhaul: Transitioning to Verifiable State Architecture

This precedent leaves corporate engineering and legal teams with an immediate infrastructure challenge. Because the bench was ruling on a specific banking appeal, it did not issue a universal technical guide on what specific electronic records satisfy the evidentiary threshold.

To mitigate legal risk, transaction tech stacks must transition away from fire-and-forget asynchronous batching. Legacy systems routinely log a transaction as completed the moment an internal database changes state. Under the court's strict standard, engineers must design bidirectional state verification directly into payment APIs.

Practically, this means engineering automated Webhook handshakes that require the receiving bank’s API to return a cryptographically signed receipt acknowledging clear funds availability. Until the Central Bank of Kenya or industry regulators formalize explicit compliance standards, corporate finance departments must rely on these real-time, cross-platform validation steps to prove payment in a court of law.