The Contract Problem Hiding Inside Nigerian Banks

A Nigerian bank's legal department is managing hundreds of active contracts at any given time.

Vendor agreements. SLAs with technology providers. Outsourcing contracts with third-party operators. Employment and consultancy agreements. Regulatory compliance contracts. Interbank agreements. Real estate leases for branches across multiple states. All of that, at once, continuously, for an institution that is also running litigation, regulatory correspondence, internal advisory work, and board-level documentation through the same team.

The contracts are not the only thing on their desk. But they are the thing that never goes away.

The problem people see — and the one they don't.

When bank executives talk about their legal function's problems, they name the visible ones: the time it takes to review a contract, the approval backlog, the cost of external legal support when internal capacity cracks under pressure.

Those are real. But they are downstream of something less visible — a contract management infrastructure that was never built to operate at the scale it is now being asked to run.

A Tier 1 Nigerian bank operates across multiple subsidiaries, multiple geographies, and multiple regulatory jurisdictions simultaneously. The contracts governing those operations live across email servers, shared drives, physical filing rooms, and the personal laptops of lawyers who handled specific transactions and may no longer be at the bank.

There is no single place where you can ask: what contracts are we currently operating under, when do they expire, and who is responsible for each one?

That question, asked of most Nigerian bank legal teams, produces a significant pause.

What visibility actually looks like inside a bank's legal department.

A senior legal officer at a Nigerian commercial bank once described contract renewals to me this way: "We find out a contract is expiring when the vendor calls to say it has expired."

Let that sit for a second.

This is not negligence. These are not incompetent people. This is the predictable result of a system where contract tracking is a manual activity handled by people who are also managing everything else. A renewal reminder is a calendar entry, if it exists at all. A contract repository is a folder structure on a shared drive, organized by whoever created it, findable only by someone who remembers where to look.

When a contract expires unnoticed, the bank lands in one of three places: operating with a lapsed agreement, renegotiating from a weak position with a vendor who knows the bank cannot switch quickly, or scrambling to execute a new contract before a regulatory examination catches it.

None of those are comfortable. All of them are avoidable. And all of them cost money in ways the institution is not tracking precisely because the visibility to track them does not exist.

The compliance layer makes it more complex.

The compliance layer is where this gets genuinely expensive.

Nigerian banks operate under CBN regulations, NDPR requirements, and for those with international operations, additional jurisdictional obligations.

Many of their vendor contracts have data protection clauses, audit rights, and service level commitments the bank is obligated to monitor and enforce.

Monitoring those obligations requires knowing what the contract says. Knowing what the contract says requires being able to find the contract. Finding the contract, in a system with no unified repository, requires knowing who handled it, when it was signed, and where they stored it.

That chain breaks regularly. The compliance obligation exists on paper. The actual monitoring of it is a different story.

From the outside, the bank appears to be in compliance. From the inside, the legal team is managing a massive surface area of contractual obligation with tools that were never built for that job.

The scale of the problem compounds itself.

A single contract mismanaged is recoverable. Hundreds of contracts mismanaged across subsidiaries and jurisdictions creates a risk profile that is genuinely hard to quantify, because the visibility to quantify it does not exist.

That is the real problem. Not any one contract. The accumulated weight of a system running without the infrastructure it needs, quietly, in ways that only become visible when it is too late to fix them cleanly.

What an observer notices.

Everyone I have spoken to inside these institutions knows the system is insufficient. That is not the hard part.

The hard part is ownership. The hard part is that contract management is not quite legal, not quite IT, not quite operations. It lives in the gap between functions. Nobody owns it completely, so nobody solves it completely. The organization keeps running because it has to, and the workarounds hold until they do not.

The banks starting to address this are not doing it because of a crisis. They are doing it because someone inside the institution, usually a GC or CIO who has done the math, realized that the cost of continuing this way is not actually lower than the cost of changing. The number, when you calculate it honestly, is not small.

That calculation, ownership, and the will to see change through inside an institution already running at capacity — that is where the real work is.

And that work is harder than buying a new tool.

***

Part of an ongoing look at how Nigerian organizations actually operate — not how their org charts say they do.