Oracle's opening Siebel finding is a maximally inflated quote, not a bill. This is the specific evidence pack that reduces it, assembled in the order that protects you.
Oracle's opening Siebel finding is a maximally inflated quote, not a bill. This is the specific evidence pack that reduces it, assembled in the order that protects you.
An Oracle Siebel audit does not open with a number you owe. It opens with a number Oracle wants. Across audit portfolios, the average initial claim runs about 4.2 times the eventual settlement, roughly a 76 percent reduction from first finding letter to signed close (Atonement Licensing, December 2025). A second advisory portfolio reports a median reduction near 71 percent (OracleNegotiations.com, December 2025). Both numbers say the same thing: the finding report is the opening position of a commercial negotiation, and every line is contestable on technical, contractual, or factual grounds.
What moves the number from Oracle's opening to your close is not eloquence. It is evidence. The buyer who arrives with a reconciled entitlement position, a clean user census, and native usage data controls the conversation. The buyer who runs Oracle's collection scripts unreviewed and waits for the report hands Oracle its evidence base and negotiates from behind it. This page sets out the exact evidence pack, and the sequence in which you build it, before Oracle sees a single row of your data.
Siebel audits are run by Oracle's License Management Services, rebranded under GLAS (Global Licensing and Advisory Services) to position compliance as a service (Redress Compliance, April 2026). The rebrand does not change the reporting line. LMS reports through the same chain as the sales organization, and the closing conversation is run jointly with your named account manager (OracleNegotiations.com, December 2025). In commercial terms, a finding letter is a quote written by the same house that sells you the remedy.
That structure tells you two things. First, the finding will apply Oracle's most aggressive reading of every metric, processor rule, and entity boundary, because inflation is the point. Second, the scripts Oracle asks you to run become its primary evidence base. Enterprises should not run Oracle's collection tools without specialist review of scope, configuration, and output (Atonement Licensing, December 2025). The tools over-count, particularly in virtualized environments, and once the output is Oracle's evidence, you are arguing against your own submission.
A Siebel finding letter is a quote written by the same house that sells you the remedy. Treat every line as an opening position, not a bill.
Oracle licensing rests on a master agreement (OMA, or the older OLSA) plus one or more ordering documents. The ordering document carries the specific programs, metrics, and quantities you actually bought; the operational rules sit in referenced policies Oracle can revise over time (Redress Compliance, June 2025). Your first evidence artifact is not usage data. It is a reconciled entitlement position built from the signed orders.
Map the ordering document to the definitions line by line, paying particular attention to product names and metrics (House of Brick, February 2026). Siebel product names are precise and the metrics are not interchangeable. A Siebel CRM Base Application license under Application User is a different entitlement from a module licensed under Processor or Registered User. Confirm which entity signed each order and which legal entities the audit scope actually covers, because Oracle routinely reads entity scope broadly to sweep in affiliates the contract never named. For a full walkthrough of the metric question, see the Siebel CRM licensing buyer guide and the specific analysis in Application User versus Employee metric.
| Evidence artifact | Source | What it proves | Priority |
|---|---|---|---|
| Signed ordering documents | Your procurement archive | Programs, metrics, quantities purchased | First |
| Master agreement (OMA/OLSA) | Contract file | Audit clause, notice period, scope limits | First |
| Metric-to-order mapping | Built by you | Which count applies to which product | First |
| User census (active accounts) | Siebel admin export | Authorized users vs current employees | Second |
| Application Usage Pattern Tracking | Siebel UPT (2015+) | Actual access by user, feature, frequency | Second |
| Module deployment inventory | Siebel repository objects | Which modules are actually configured | Second |
| Restricted-use DB evidence | Oracle DB config | Database used only for Siebel | Supporting |
Siebel CRM primarily uses the Application User metric, defined as any individual authorized to access the application, irrespective of actual frequency or duration of use (Oracle Licensing Experts, June 2025). The metric counts authorization, not activity. If you have 500 employees but only 150 use Siebel regularly, you still license every individual with authorized access, not just the regular users.
The single largest Siebel audit trap follows directly from this. Every account with an active Siebel login is licensable, whether it is used or not, and Siebel does not enforce license limits by default (Oracle Licensing Experts, July 2025). Failing to end-date departed employees inflates the count Oracle deems licensable. The concrete exposure is stark: 500 active accounts against 400 current employees produces 100 licenses of pure administrative debris (Redress Compliance, July 2025). Oracle sees 500 required. The responsibility to clean the list is yours, and no one has done it.
Your defensive move is a reconciled user census built before Oracle counts. Export every active Siebel account, cross-reference against current HR headcount and joiner/leaver records, and deactivate every account tied to a departed employee, a duplicate, a test identity, or a service account that does not require licensing. Do this before any snapshot Oracle relies on. A user count reduced from 500 to the genuine 400 is a 20 percent reduction in the licensable population, secured with an SQL export and an HR reconciliation, not a negotiation.
An active login you forgot to deactivate is a full-price license in Oracle's count. The cheapest reduction in a Siebel audit is a clean user list.
External non-employee users cannot use an internal Application User license. Oracle offers a Registered User metric for them, or you license by Processor for external-facing portals (Oracle Licensing Experts, May 2025). Auditors probe this hard because portals blur the line. Document contractors and partners against the correct metric before the audit forces the classification; the counting logic is set out in counting contractors and external users. Note also that Siebel partner options are capped to the Partner Portal quantity: if you hold 100 Partner Portal licenses, Partner Commerce must be 100 or fewer (Oracle Global Price List, November 2024). That cap is a rule Oracle can use against you, and occasionally a ceiling you can use in your favor.
From Siebel CRM Innovation Pack 2015 onward, Application Usage Pattern Tracking (UPT) ships out of the box. It captures who accessed which UI or feature, when, and how many times (Siebel Mantra, May 2016). This is buyer-side gold. It lets you demonstrate actual usage against authorized access, and it lets you build a defensible picture of which modules are genuinely in use.
UPT matters because Siebel does not technically prevent an administrator from granting access to modules you never bought. An admin can unknowingly enable a view belonging to another module, and Oracle's scripts will detect usage of objects across all modules during the audit (Oracle Licensing Experts, July 2025). Module sprawl is a top-three Siebel finding, examined in Siebel module sprawl and audit findings. UPT combined with a repository object inventory lets you distinguish a module that is deployed and used from a stray view that a configuration error exposed. That distinction is worth real money: an add-on can list at $1,080 per Application User with a 25-user minimum (Oracle Real-Time Decisions for Siebel), and integration packs reach $43,499 per Processor (Oracle price list archive).
You cannot judge whether a finding is inflated without the list values behind it. The Siebel CRM Base Application lists at $3,750 per Application User (Software Finder, June 2026), and every user requiring a base must hold one (Oracle Global Price List, January 2024). Industry verticals stack on top: if you run an industry solution, all users need the industry base option plus the Siebel CRM Base (Oracle Global Price List). The model is modular and per-user, so costs compound quickly, with list prices in the thousands per user across the stack (Oracle Licensing Experts, July 2025).
| Component | List price | Metric | Note |
|---|---|---|---|
| Siebel CRM Base Application | $3,750 | Application User | Mandatory, at least one per user needing a base |
| Real-Time Decisions (Intelligent Offer) | $1,080 | Application User | Minimum 25 users |
| Integration Pack (Order Management) | $43,499 | Processor | Per-processor, high-impact in findings |
| Industry base option | Varies | Application User | Stacks on the CRM Base for vertical solutions |
Two cautions. First, list price is a ceiling for negotiation, not a floor; existing customers rarely pay list, and a finding priced at list is negotiable on price alone. Second, remember the database. The Oracle Database bundled under Siebel is usually a restricted-use license, and stepping outside those limits creates separate exposure that auditors treat as a distinct claim. The boundaries are set out in the Oracle Database under Siebel restricted-use limits.
The audit clause typically gives Oracle the right to verify usage on 45 days written notice, with a broad cooperation obligation (Redress Compliance, June 2025). The notice period and scope are negotiable at signature and rarely afterward, so read what you actually signed. Critically, Oracle's agreements grant audit rights but usually do not specify the exact methodology or tools. You have the right to use your own tools and provide Oracle a curated data set that fulfills the contractual obligation without providing more than required (Oracle Licensing Experts Audit Guide, March 2026).
If the audit outcome pushes toward a large true-up, remember that support strategy is a lever too. Whether to stay on Oracle support, walk toward Fusion, or move to a third party changes the math of any settlement. See Siebel on third-party support and migrating from Siebel to Fusion CX before agreeing to any multi-year commitment tied to the audit close.
Build the evidence pack in strict order. First, reconcile entitlement from the signed orders and map every product to its metric. Second, run a user census and deactivate every account not tied to a current, licensable individual, before any snapshot Oracle relies on. Third, extract UPT and a module inventory to separate genuine deployment from configuration accidents. Fourth, control the process: review before you run anything, curate what you submit, and extend the timeline. The 71 to 76 percent gap between Oracle's opening and the eventual settlement is not luck. It is the difference between a buyer with evidence and a buyer without it.
Usually no. Oracle's agreements grant audit rights but typically do not mandate specific tools or methodology. You can use your own tools and provide a curated data set that meets the contractual obligation without providing more than required. Running Oracle's scripts unreviewed hands Oracle its primary evidence base, so review scope, configuration, and output first.
Siebel uses the Application User metric, which counts anyone authorized to access the application regardless of usage. Every active login is licensable whether or not it is used, and Siebel does not enforce limits by default. Departed employees whose accounts were never deactivated inflate the count Oracle deems licensable, which is the single most common source of invented exposure.
Portfolio data shows the average initial Oracle audit claim runs about 4.2 times the eventual settlement, roughly a 76 percent reduction, with a corroborating median near 71 percent. The reduction is driven by evidence: a clean user census, reconciled entitlement, and native usage data, not by negotiation alone.
UPT ships out of the box from Siebel CRM Innovation Pack 2015 onward and records who accessed which feature, when, and how often. It lets you prove actual usage against authorized access and separate genuinely deployed modules from stray views a configuration error exposed. That distinction directly caps module-sprawl findings.
In most cases no. Oracle typically requests a response within 30 days, but that deadline is generally not contractually binding and can be extended through negotiation. Most material-reduction settlements take 8 to 16 weeks to close from the finding letter, so refusing artificial urgency is part of the defense.
The master agreement (OMA or older OLSA) plus your ordering documents. The ordering document carries the specific programs, metrics, and quantities you bought; the master agreement sets the audit clause, notice period, and scope. Mapping product names and metrics from the orders to the definitions is the first evidence artifact you build.
The strategic framework for Oracle audit defense across LMS, license verification, and contractual response. Beyond the tactical playbook.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
