Agent liquidity: Nigeria’s hidden last-mile infrastructure

Agent banking has expanded financial access by placing everyday services closer to homes, markets and workplaces. But proximity alone does not guarantee availability. When an agent cannot fund a withdrawal or complete a customer request, the service point exists physically while failing operationally.

Liquidity is the agent’s operating inventory

A retailer cannot trade without stock. In the same way, an agent cannot provide cash-out services without sufficient cash and cannot support deposits or transfers without adequate electronic float. Liquidity is not a side issue; it is the inventory that makes the outlet functional.

This is especially important where customer demand is uneven. Salary days, market days, mornings, evenings and local commercial activity can produce sharp liquidity swings. A location may look profitable on average while still losing customers during its most valuable hours.

What liquidity failure looks like

Crest’s field observations across Lagos repeatedly show that agents manage shortages through informal workarounds: borrowing from another agent, sourcing cash from nearby businesses, asking customers to wait or turning transactions away.

These responses keep some transactions alive, but they create hidden costs:

• customers leave for competing agents;
• operators spend time searching for cash instead of serving customers;
• unstructured borrowing weakens accountability;
• cash movements increase security exposure; and
• the network loses a clear view of unmet demand.

The lost transaction is only the visible part of the problem. Repeated unavailability also damages trust in the service point.

Liquidity support must be a controlled system

Providing more cash without operating controls simply increases exposure. A responsible liquidity model should connect funding to verified transaction behaviour, clear custody rules and daily evidence.

A practical system should define:

• the agent’s normal opening cash and electronic float;
• peak deficit periods and the typical size of the shortfall;
• approved replenishment and repayment procedures;
• cash limits, dual controls and incident escalation;
• daily reconciliation and exception review; and
• the conditions for increasing, reducing or withdrawing support.

The objective is not to maximise the amount of cash in the field. It is to place the right amount of liquidity at the right node, at the right time, under controls that protect the agent and the funding partner.

What a pilot should measure

A liquidity pilot should test whether additional working capital creates measurable operating value. At minimum, the pilot should capture:

• completed and failed transactions by service type;
• customers turned away because cash or float was unavailable;
• time and cost required to restock liquidity;
• transaction revenue before and after support;
• daily reconciliation accuracy and repayment performance;
• network downtime, fraud attempts and security incidents; and
• the hours and days when support creates the greatest value.

These measures separate a genuine liquidity constraint from other causes of weak performance such as poor location, limited footfall, network instability, pricing or operator behaviour.

Scale only what the evidence supports

The strongest agent network is not necessarily the one with the most terminals. It is the one that can deliver consistent service while controlling cash, risk and operating cost.

Liquidity should therefore be treated as infrastructure: mapped, monitored and governed. When institutions can see where shortages occur and what revenue is being lost, they can direct resources more intelligently and build stronger networks from the field upward.

This article is for general information and operational education. It is not personalised financial, investment or credit advice.