Oracle Pool of Funds licensing. How to spend the balance before it expires.

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 spend before the term ends.

What is an Oracle Pool of Funds?

An Oracle Pool of Funds (PoF) is a prepaid balance that you draw down against a fixed price list during a defined term. When the balance is spent or the term ends, the deal is over, and any unspent portion is lost.

You pay the full amount up front. Each eligible deployment is then charged against the balance at the net rate written into the agreement. Anything you have not drawn by the expiry date does not carry into the next contract.

How a drawdown works during the term

1. You deploy an eligible product on a server or for a group of users.
2. You record the deployment, the metric (processor or Named User Plus) and the quantity.
3. The drawdown is valued at the locked net rate for that product and metric.
4. That value comes off the prepaid balance, and the deployment becomes part of your licensed position.
5. At term end, both sides reconcile what was drawn, and the remaining balance expires.

Your ordering document may also require usage reports during the term, and it sets the deadline for the final declaration after expiry. Read both terms before the first deployment, because they decide how often your records must be ready.

Why a Pool of Funds is so often governed like a ULA

The confusion is understandable. A Pool of Funds sits next to the Oracle Unlimited License Agreement in Oracle's portfolio and is sold with similar language about flexibility. The mechanics run in opposite directions.

Which two numbers decide whether an Oracle Pool of Funds pays off?

A Pool of Funds succeeds or fails on the rate you draw down at and on how much of the prepaid balance you spend before it expires. Buyers negotiate the first, sometimes hard. Very few govern the second, and it is where most of the value is lost.

Money left in the pool at expiry was paid at signature and buys nothing. No discount on the rate can offset that, because the entitlement the money would have bought is never taken.

What the locked price list protects, and what it does not

Prices locked at signing are a hedge against increases for the whole term. A locked rate is only valuable relative to what you would otherwise have paid, though. If the list was set without benchmarking, the lock preserves an expensive list for every year of the agreement.

That makes benchmarking a precondition of signing. Compare each rate on the draft rate card with what comparable buyers pay for the same product and metric, using current Oracle license cost benchmarks, before the rates become fixed.

What does an unspent balance cost in a worked example?

An unspent balance raises the real price of every license you did draw, and it can erase much of the discount you negotiated. The hypothetical below uses Oracle Database Enterprise Edition, which lists at $47,500 per processor license on Oracle's technology price list, with support at $10,450 a year.

Say you sign a $1,900,000 pool with a three year term. The rate card gives you Database Enterprise Edition at $19,000 per processor, 60 percent off list, and your plan says you will deploy 100 processors. A delayed program means you draw only 80.

In the second row, $1,900,000 divided by 80 processors is $23,750 each, which is 50 percent off list. The 60 percent discount you negotiated turned into 50 percent once the forfeit is counted.

The last row assumes a benchmark showed $15,200 was achievable, so the signed $19,000 rate sat 25 percent above it. On the same 80 processors, the gap between the second and last rows is $684,000, or 36 percent of the original pool.

How support can add to the loss

Check how your order calculates support. Oracle prices support as a percentage of the net license fee on the order, and in a pool that fee can be the full pool value from the start date, drawn or not. The list support rate is 22 percent of the license fee.

In the example, 22 percent of the $380,000 you never drew is $83,600 a year, or $250,800 over the three year term, paid on licenses you do not hold. Ask for support to start at each drawdown instead, or to be based on drawn value only.

What have we seen in Oracle Pool of Funds deals in 2024 and 2025?

Weak drawdown tracking caused most of the value loss. We reviewed roughly 15 to 25 Oracle Pool of Funds deals over 2024 and 2025, and three patterns came up again and again.

• Balance expired unspent. Buyers left 10 to 25 percent of the prepaid balance undrawn at expiration, and it was lost outright.
• Rates set without a benchmark. Drawdown rates negotiated without benchmarking ran 15 to 30 percent above what was achievable, and were then locked for the full term.
• No internal ledger. Buyers who kept no record of their own drawdowns faced certification surprises of 20 percent or more at term end.

Each of these losses was visible early in the term. It became expensive because the first serious look came at certification, when no term was left to fix it.

How should you size an Oracle Pool of Funds?

Size the pool against a deployment plan you believe. The plan that justifies the largest discount is usually the one that leaves money in the pool at expiry, and the worked example shows what that forfeit does to your real price.

Start from named projects with owners, dates and product lists. Add the growth you can tie to a funded program. Leave out capacity that exists only as a hope in a strategy deck, because the pool will charge you for it either way.

Why we advise against the largest pool for the deepest discount

The usual advice is to commit as much as you can, since a larger pool earns a deeper discount off list. We disagree when the extra volume is uncertain. Size the pool to your firm plan and negotiate a right to add funds later at the same rates, so extra processors cost nothing until you need them.

Suppose Oracle offers 65 percent off list, $16,625 per processor, for a 100 processor pool instead of 80. That pool costs $1,662,500, or $20,781 for each of the 80 processors you actually draw. The 80 processor pool at 60 percent costs $1,520,000, so the extra 5 points of discount cost you $142,500.

How the approach changes with the size of the pool

• A small pool tied to one program. A single project delay can strand a large share of the balance. Keep the term close to the project timeline and the product scope narrow, and ask for an extension right in case the go live date slips.
• A large pool shared across business units. The risk is that each unit assumes another will consume the balance. Allocate the pool to units, set quarterly drawdown targets per unit, and keep one central ledger.
• A pool running alongside other Oracle agreements. Confirm which contract each deployment draws against, so a license bought under an older agreement is not also counted against the pool.

How do you govern the balance during the term?

Govern it monthly, against a written drawdown plan, with your own ledger as the record. Give one person ownership of both, usually the software asset manager, with a finance contact who signs off the balance each quarter.

• Plan by quarter. Spread the planned drawdowns across the term so a monthly check shows a gap in weeks, when there is still term remaining to use it.
• Record at deployment. Add each drawdown to the ledger when the server or user group goes live, instead of assembling the history at certification.
• Check scope before go live. Anything outside the eligible list is a separate purchase at rates the pool does not protect, and a drawdown you assumed was covered may not be.
• Escalate early. If drawn value falls more than a quarter behind plan, bring it to the program sponsor with a choice: pull deployments forward or use an extension right.

What the deployment ledger should record

Oracle keeps its own record of what you drew. Without an internal one, the reconciliation at term end arrives as a claim from Oracle, and buyers in that position met the surprises described above. The certification mechanics are covered in our Oracle audit response guide.

Building the ledger is not sophisticated work. It is a record of what was deployed, against which entitlement, on which date, kept up continuously. For each drawdown, capture enough to match a line in Oracle's drawdown record without discussion:

• the deployment date and the declaration date
• the product, the metric and the quantity
• the net rate applied and the balance remaining afterward
• the host, cluster or user population, with its processor count or named users
• the legal entity and location that owns the deployment
• the Customer Support Identifier (CSI) the license sits under in My Oracle Support

How to check what you have actually deployed

Compare the ledger with the systems themselves each quarter, using the sources Oracle's auditors rely on.

• Oracle's collection scripts. The scripts Oracle's audit team supplies for license reviews report installed products, options and processor data, and you can rerun a copy from an earlier review yourself. Our analysis of the LMS audit scripts explains what they collect.
• DBA_FEATURE_USAGE_STATISTICS. This database view shows which options and management packs have been used, which catches drawdowns you did not plan.
• Oracle Enterprise Manager. Its host and target inventory gives current processor counts for the servers in the ledger.
• My Oracle Support. The CSI records show what Oracle holds as your licensed and supported position.

Our guide to reconciling Oracle entitlements to deployment covers the matching step in more detail.

Timeline from signature to final declaration

What should you negotiate into an Oracle Pool of Funds contract?

Negotiate the rate card, the scope and the treatment of unspent balance before you sign, because the ordering document fixes all three for the term.

Contract terms to ask for

• A full rate card as an exhibit. Every eligible product, metric and net unit price in writing, so there is no dispute about what a drawdown costs.
• The right to add products at the same discount. A product missing from the list otherwise becomes a separate purchase at full negotiation.
• An extension or carry forward of unspent balance. Either one converts a forfeit into a delay if a program slips.
• A top up right at the locked rates. With it, a conservatively sized pool keeps the same discount level.
• Support that starts at drawdown. Paying support on money you have not spent inflates the cost of the pool.
• Scope that covers all your entities and locations. Name every affiliate and country, and confirm whether drawn licenses may run in authorized cloud environments.
• A cap on support increases. The pool locks license rates, while support uplift is set separately. Our note on price hold and uplift caps covers the wording.

A locked price list protects you against increases. It does nothing for a list you overpaid for, and nothing for money you never spend.

What the Oracle account team will say, and what to say back

• "A bigger pool earns a bigger discount." Ask for the rate card at the pool size your plan supports, plus the right to add funds later at the same rates.
• "We can look at unused funds nearer the end." Ask for the extension or carry forward to be written into the order now, while you still have something Oracle wants.
• "Deploy what you need and we will sort it out at the declaration." Reply that you will declare against your own ledger, and ask for a quarterly drawdown statement to be written into the order so you can compare the two during the term.

What to do next

1. Benchmark the drawdown list before you sign. The lock preserves it for the full term either way.
2. Size the pool to a deployment plan you believe. Negotiate a top up right at the same rates instead of a larger pool.
3. Open the deployment ledger on day one. Record entitlement, date, metric, quantity and host for every drawdown.
4. Review the balance against plan every month. Underspend then surfaces while there is still term left to use it.
5. Reconcile with Oracle's record six months before expiry. Settle differences before the final declaration is due.
6. Prepare certification as a comparison of two records. Our Oracle advisory team can build the ledger with you, and the Oracle knowledge hub holds the wider library.

Frequently asked questions