The audit script counts named accounts, but the old paper licenses concurrency
An estate holds 300 Concurrent User licenses, carries 850 named accounts, and measures peak concurrency at 180. That estate is compliant with headroom. The standard audit script reports 850, and the finding, the pressure, and the conversion offer are all manufactured from that one misread.
Prepared by Redress Compliance · August 14, 2026 · Oracle licensing advisory. EBS entitlement archaeology across legacy estates, 2024 to 2026.
Executive summary
A concurrency metric can lawfully cover a named population several times its size. A 300 Concurrent User contract supports any named population whose peak simultaneous use stays at or under 300, which is exactly why conversion offers keep arriving.
Standard audit scripts count named accounts, which is not what concurrent paper licenses. The gap between 850 accounts and 180 peak concurrent users is not a compliance gap, it is a measurement error, and it becomes a finding only if nobody in the room can prove the peak.
The defense is a dated record, built before any letter arrives: the EBS sign on audit captured at session level, sampled across at least a full quarter including period close, filed with the method. A dated internal record beats any reconstruction produced under audit pressure.
Your paper governs, not the current price list. Oracle's metric definitions are year versioned, and entitlement is the sum of thirty years of orders, master agreements, amendments, and migration documents, not whatever the last renewal quote says.
No deadline forces a conversion. EBS 12.2 is committed to at least 2037, a renewal continues the existing base, and a conversion is the one event that reopens it, recalculating support on the replacement licenses and typically stripping legacy discounts. Any urgency is commercial, not technical.
What the old metrics actually say
| Element | How it reads | Buyer note |
|---|---|---|
| Concurrent User | Licenses peak simultaneous use, not people | 850 named accounts on 300 seats is lawful at peak 300 or under |
| Concurrent Device | The device variant of the same concurrency logic | Read the definition in your paper, not the modern glossary |
| Year versioned definitions | Oracle's metric definitions changed era by era | The definition in force at purchase governs your entitlement |
| The document chain | Orders, master agreements, amendments, migrations | Entitlement is the sum of the chain, not the last renewal quote |
| The audit script | Counts named accounts | Not the licensed quantity on concurrent paper; hold the definition in the room |
| Migration paperwork | Each past migration redefined something | Part of the chain, not an appendix; find it before Oracle asks |
The concurrency record is the entire defense, and it must predate the letter. Capture the EBS sign on audit at session level, sample it across at least a full quarter including period close, and file the peak figure with the documented method and a date. Under audit pressure, a reconstruction is an argument; a dated record is a fact.
The moves that hold the position
- Measure concurrency on your own terms, now. Session level sign on data across a full quarter, period close included, filed with the method. Do it before any audit letter arrives.
- Rebuild the document chain: original orders, the master agreement in force at each purchase, every amendment, and every prior migration document, in date order. Thirty years of paper is the entitlement.
- Hold the definition in the room. When the script output arrives, the response is the metric language from your order, next to your dated peak record, not a defense of the account count.
- Run the replacement cost test before trading old paper: what would the same entitlement cost bought today, and what does the conversion strip, starting with the legacy support discounts.
- Refuse commercial urgency. With EBS 12.2 committed to at least 2037, the only good time to convert is when Oracle wants something from you, priced by your register, on your calendar.
The Oracle audit response playbook
The audit letter sequence, the data control rules, the entitlement defense method, and the settlement mechanics for Oracle compliance reviews.
Get the playbook →The conversion offer prices your ignorance
Why does an estate running quietly on twenty year old EBS paper keep receiving conversion offers? Not because the old licenses stopped working, and not because support is ending, since EBS 12.2 runs to at least 2037. The offers arrive because of what the old paper contains: headroom Oracle can only recover if you surrender the metric.
A concurrency license is one of the last places in enterprise software where the buyer holds a structurally favorable unit. It prices simultaneous work, and a workforce three times the seat count can lawfully share it. Every modern metric Oracle would convert you to prices people or processors, and the difference between those two denominators is the value of your paper.
The audit script is what turns that value into pressure. By counting named accounts against a concurrency grant, the script produces a number, 850 against 300, that looks like an enormous finding and is actually a category error. An estate that cannot produce its own peak figure has no way to say so, and an estate under a manufactured finding finds the conversion offer suddenly reasonable: trade the old paper, and the problem the script invented goes away.
Seen whole, the sequence is one mechanism, not three events. The misread creates the exposure, the exposure creates the urgency, and the conversion resolves the urgency by moving you onto metrics that price your whole population, with the support stream recalculated on the replacement licenses and the legacy discounts stripped in passing.
The dated concurrency record breaks the mechanism at its first link. With a defensible peak on file and the year versioned definition held in the room, the script output is not a finding, it is a spreadsheet, and the conversion conversation returns to what it always should have been: a trade, priced by the replacement cost test, taken only when Oracle wants something and your register says the terms are worth it.
The audit context sits in hidden Oracle audit risks and the Oracle audit guide; the wider position in the Oracle practice.
Watch the briefing · 4:30How to Negotiate an Oracle ULA: No Price List, Just Your Business CaseThe commit shape conversion offers often lead to: why the fee is a story built from your estate, and the certification exit to negotiate before signature.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
The worked estate, and the patterns around it
The worked estate makes the arithmetic concrete: 300 Concurrent User licenses, 850 named accounts, peak concurrency measured at 180 across a full quarter including period close.
Measured peak simultaneous use, documented with method and date: compliant on 300 seats with 120 seats of lawful headroom.
Named accounts, which concurrent paper does not license, and the raw material of every manufactured finding.
Three patterns recur across legacy EBS estates. No concurrency register, so the script's count stands unopposed. Document chains scattered across decades of storage, so entitlement gets argued from the renewal quote instead of the orders. And conversions accepted under audit pressure, at the one moment the pricing is guaranteed to be worst.
The buyer side move is archaeology before arithmetic. The wider library sits in the Oracle practice.
Your first five moves
- Start the concurrency register this quarter: session level sign on capture, a full quarter's sampling including period close, the peak filed with method and date.
- Assemble the document chain in date order: orders, master agreements, amendments, migration paperwork. Store it where an audit response team can reach it in a day.
- Write the entitlement register from the chain: metric, quantity, definition version, and entity scope per line, so the position is stated before anyone else states it for you.
- Run the replacement cost test on the old paper so any conversion conversation starts from what the entitlement is worth, not from what the finding threatens.
- Answer any script output with the definition and the register, not with raw data. The Oracle practice runs the defense and the conversion math with you.
Frequently asked questions
What does an Oracle EBS Concurrent User license entitle?
Peak simultaneous use, not named accounts. A 300 Concurrent User contract lawfully supports any named population whose peak simultaneous use stays at or under 300, which means a concurrency metric can cover a named population several times its size.
Why do Oracle audits misread concurrent licenses?
Because standard audit scripts count named accounts, which is not what concurrent paper licenses. An estate with 300 Concurrent User licenses, 850 named accounts, and a measured peak of 180 is compliant with headroom, but the script reports 850 and the finding is manufactured from the mismatch.
How do you build a defensible concurrency record?
Capture the EBS sign on audit at the session level, sampled across at least a full quarter including period close, and file the peak figure with the documented method and a date. A dated internal record beats any reconstruction produced under audit pressure, and it should exist before any audit letter arrives.
Which license definitions govern an old EBS contract?
The definitions in your paper. Oracle's metric definitions are year versioned, and entitlement is the sum of the original orders, the master agreement in force at each purchase, every amendment, and every prior migration document. The last renewal quote is not the entitlement.
Is there a deadline forcing EBS license conversion?
No. EBS 12.2 is committed to at least 2037, so no technical deadline forces a conversion decision. Any urgency attached to a conversion offer is commercial, not technical.
What does converting legacy EBS licenses actually cost?
The support stream is recalculated on the replacement licenses, which typically strips legacy discounts, and the concurrency headroom is surrendered with the old metric. A renewal continues the existing base; a conversion is the one event that reopens it.
When should a buyer consider an EBS conversion offer?
Only from a verified position and on your own timing. A compliant estate on old definitions can time any conversion to the moment Oracle wants something, which is the only time conversions price well, and should first run the replacement cost test so the old paper is traded for value the buyer priced.
Application Users: Authorisation, Not Activity
Session 2 of the Oracle EBS Licensing Series. An Application User is a named individual authorised on a module, whether or not they ever log in, and one person on four modules is four licences. The dormant thirty to forty percent, the reconciliation that cuts counts by a fifth to a third, and the legacy concurrent paper that audit scripts systematically misread.
