Buyers left 10 to 25 percent of the balance unspent at expiration, and the locked price list only protects you if it was negotiated

A Pool of Funds looks like flexibility and behaves like a prepaid balance with an expiry date. Two numbers decide whether it pays: the rates you draw down at, and how much of the balance you actually spend before the term ends.

Prepared by Redress Compliance · August 17, 2026 · Oracle advisory. 15 to 25 Oracle Pool of Funds deals reviewed, 2024 to 2025.

The instrument is simpler than its reputation and stricter than buyers expect. It is a prepaid balance, drawn down against a fixed price list, for a defined term.

A Pool of Funds pays or fails on two figures. The first is the rate you draw down at, which is locked at signature and applies for the term. The second is how much of the prepaid balance you actually spend before it expires. Buyers negotiate the first, sometimes hard, and almost nobody governs the second. Across the deals reviewed, 10 to 25 percent of the balance was left unspent at expiration and lost outright, which is a loss no discount on the rate can offset.

The rate protection also deserves a closer look than it usually gets. Prices locked at signing sound like a hedge against increase, and they are, but a locked rate is only valuable relative to what you would otherwise have paid. Drawdown rates negotiated without benchmarking ran 15 to 30 percent above achievable in the deals reviewed, which means the lock preserved a bad list for the full term. The protection is real and it is conditional on the list being right in the first place, which makes benchmarking a precondition rather than an optional refinement.

The ledger problem is the third and it compounds both. A PoF requires you to know what you have drawn against the balance, and Oracle records its side of that. Estates with no internal ledger met certification surprises of 20 percent or more at term end, because the reconciliation arrives as a claim rather than a comparison. Building the ledger is not sophisticated work. It is a record of what was deployed against which entitlement on what date, maintained continuously, and it is what turns certification into an arithmetic exercise rather than a negotiation.

The practical shape of a well run PoF is therefore quite different from how it is usually managed. Benchmark the drawdown list before signing, because the lock preserves whatever you agree. Track the balance monthly against a plan, so underspend is visible while there is still term left to correct it. Maintain the deployment ledger from day one rather than assembling it at certification. And size the pool against a deployment plan you believe rather than the one that justifies the discount, since an oversized pool converts a discount into a forfeit. The certification mechanics sit in the audit response playbook, and the wider library in the Oracle practice.

• Benchmark the drawdown list before signature, because the rate lock preserves whatever list you agree, for the whole term, whether or not it was competitive.
• Track the balance monthly against a drawdown plan, so underspend becomes visible while there is still term remaining to correct it.
• Maintain a deployment ledger from day one, recording what was deployed against which entitlement on what date, rather than assembling it at certification.
• Size the pool to a deployment plan you actually believe, since an oversized balance converts a headline discount into a forfeit at expiry.
• Confirm the eligible product scope, because anything outside it is a separate purchase at rates the pool does not protect.
• Do not govern it like an unlimited agreement. The mechanics are opposite, and treating a finite prepaid balance as though deployment were free is how the underspend accumulates.

Across roughly 15 to 25 Oracle Pool of Funds deals reviewed, weak drawdown tracking caused most of the value loss:

Estates with no internal ledger faced certification surprises of 20 percent or more at term end, because the reconciliation arrives as a claim rather than as a comparison between two records.

The instrument is a prepaid balance drawn down at locked prices during a term. It is not unlimited, and when the balance is spent or the term ends, the deal is over.

What is an Oracle Pool of Funds?

A prepaid balance you draw down against a fixed price list during a defined term. It is not an unlimited agreement. When the balance is spent or the term ends, the deal is over and any unspent portion is lost.

How much of the balance typically goes unspent?

Between 10 and 25 percent across the deals reviewed. That is a loss no rate discount can offset, because the money was paid at signature and the entitlement it would have bought is never taken.

Does the locked price protect us?

Against increases, yes. Against a bad list, no. Drawdown rates negotiated without benchmarking ran 15 to 30 percent above achievable, and the lock then preserved that list for the full term.

Why do estates get certification surprises?

Because they have no internal ledger. Oracle records its side of the drawdown, and without your own record the reconciliation arrives as a claim rather than a comparison. Surprises of 20 percent or more were common.

What should the ledger record?

What was deployed, against which entitlement, on what date. It is not sophisticated work, and maintaining it continuously turns certification into an arithmetic exercise rather than a negotiation.

How is a PoF different from a ULA?

The mechanics are opposite. An unlimited agreement lets you deploy without counting and settles at certification. A PoF makes you count every drawdown against a finite balance that disappears at term end.

What happens if we govern it like a ULA?

The underspend accumulates. Treating a finite prepaid balance as though deployment were free is the direct route to leaving a quarter of it unused at expiry, which is the most common failure mode we see.

How should the pool be sized?

Against a deployment plan you genuinely believe rather than the one that justifies the largest discount. An oversized balance converts a headline discount into a forfeit, since the unspent portion is simply lost.

What about products outside the scope?

They are a separate purchase at rates the pool does not protect. Confirming the eligible product scope at signature matters, because a drawdown you assumed was covered may not be.

When should the balance be reviewed?

Monthly, against a drawdown plan. Annual review discovers underspend when there is too little term left to correct it, which is functionally the same as not reviewing it at all.