When Oracle Fusion Middleware 12c reaches the end of Premier Support in December 2026, you have four coherent Oracle 12c support options: buy Extended Support (through December 2027), drop to Sustaining Support (indefinite, but existing patches only), request Market Driven Support (yearly, case-by-case), or upgrade to 14c (Premier through 2030). Which one is right depends almost entirely on how long a runway you actually need and how much regulatory and security change your AP environment absorbs each year.
If you searched for what happens after 12c Premier Support ends, this is the decision that comes next. Here's what each tier covers, what it means in practical terms for an AP team running on WebCenter, and when waiting it out genuinely works — and when it doesn't.
The 12c support tiers at a glance
Oracle's support lifecycle is the same shape for every product line: Premier, then Extended, then Sustaining. For Fusion Middleware 12c, the dates line up like this:
| Tier | Availability | New security patches | New bug fixes | Tax / legal / regulatory updates | Cost posture | |---|---|---|---|---|---| | Premier Support | Through Dec 2026 | Yes | Yes | Yes | Included in your existing support contract | | Extended Support | Dec 2026 – Dec 2027 | Yes | Critical fixes only | Yes | Uplift on top of your support fee | | Market Driven Support | Yearly, renewable | Defined per agreement | Defined per agreement | Defined per agreement | Higher than Extended, approved case-by-case | | Sustaining Support | Indefinite | No new patches | No | No | Continues your support fee, but with reduced scope | | Upgrade to 14c | Premier through Dec 2030 (Extended through Dec 2033) | Yes | Yes | Yes | Project cost, then back on the standard clock |
The single most important column is "new security patches." That's where the tiers really diverge, and it's the column that should drive your decision far more than the headline dates.
What Extended Support actually buys you
Extended Support is the closest thing to "keep going as you are." For the year from December 2026 to December 2027, you continue to receive new security patches and critical bug fixes, and — importantly for AP — tax, legal, and regulatory updates keep flowing. What you don't get is the full stream of general bug fixes you had under Premier; Extended narrows to critical severity.
For most AP teams, Extended Support is a one-year bridge, and it's a clean one. If you know you'll be on 14c or on Fusion Cloud by late 2027, paying the uplift for a supported, patched year while you execute that plan is the responsible move. The math works when the bridge is short and the destination is already on the roadmap. We lay out how to structure that year in the WebCenter 12c end-of-support decision guide.
What Sustaining Support does — and doesn't — cover
This is the tier most searchers misunderstand, so it's worth being precise. Sustaining Support is available indefinitely — you never age out of it — and you keep access to Oracle's knowledge base, existing patches, and the ability to log service requests. That "indefinite" part is why it sounds attractive.
Here's the catch that matters for an AP environment: Sustaining Support gives you existing patches only. No new security patches. No new bug fixes. And critically, no new tax, legal, or regulatory updates. For an accounts payable operation, that last point is the one to sit with — if your withholding logic, tax handling, or statutory reporting depends on Oracle-supplied updates, Sustaining Support stops delivering them the moment you drop to it.
Sustaining Support is a genuinely reasonable choice in the right conditions: a low rate of change in your environment, a short remaining life for the system, and a security posture you can defend by other means (network isolation, compensating controls). It is a poor choice if you're a regulated industry expecting continuous patching, or if you're looking at a multi-year horizon on the same platform. The Sustaining Support decision walkthrough works through exactly which side of that line a given AP environment falls on.
Where Market Driven Support fits
Market Driven Support is the option most people haven't heard of, and it sits between Extended and Sustaining in intent. It's offered on a yearly, renewable basis and is approved on a case-by-case basis — Oracle evaluates the specific product, the customer base still on it, and the scope of what will be delivered. It typically carries a higher cost than Extended Support, and the exact coverage is defined in the agreement rather than fixed by the standard lifecycle.
The realistic read: Market Driven Support is a tool for organizations that need a defined, patched runway beyond the standard Extended window and have a concrete reason they can't move on the normal schedule. It's not a default; it's a negotiated arrangement. If your timeline pushes past December 2027 and Sustaining Support's scope is too thin for your compliance needs, this is the conversation to have with your Oracle account team — with a clear picture of the runway you need and why.
When waiting it out works — and when it doesn't
Strip away the tier names and the real question is: do you extend the current platform, or do you move? Waiting it out — Extended, then Sustaining, or Market Driven — makes sense in a specific shape of situation:
- It's a short bridge to a planned replacement. You already know you're moving to Fusion Cloud ERP or consolidating systems, and you need 12–24 supported months to do it deliberately rather than under deadline pressure.
- Your rate of change is low. The AP process is stable, supplier layouts are settled, and you're not depending on a steady stream of new Oracle features or regulatory updates.
- You can defend the security posture by other means during any window where you're not receiving new patches.
Waiting it out doesn't work when:
- You're in a regulated industry that needs continuous security patching. Sustaining Support's "existing patches only" scope is a real gap here, and Extended only carries you to December 2027.
- Your horizon is multi-year. If you're going to be on this platform for three-plus years, you'll spend more time outside Premier Support than in it — and the patch and regulatory gaps compound.
- Browser and OS compatibility drift is a factor. Middleware that isn't receiving new fixes will, over time, fall out of step with the browsers and operating systems your team and your auditors actually use. That drift is slow, but it's real, and no amount of Extended Support addresses it.
If two or more of those apply, upgrading to 14c is usually the better economic call, not just the safer one. WebCenter 14c (14.1.2) shipped in 2024 with Premier Support through December 2030 and Extended through December 2033 — which resets the clock and gets you a modernized engine at the same time. We walk through what that upgrade actually involves for an AP workload in the WebCenter 14c upgrade guide. To put real numbers behind the extend-versus-upgrade comparison, the WebCenter TCO calculator lets you model support uplifts and project cost side by side over your planning horizon.
Deciding on your own schedule
There's no single right answer here — there's the right answer for your timeline, your industry, and your rate of change. A short, well-defined bridge to a planned move is a perfectly good reason to buy a year of Extended Support and keep moving. A stable, low-change environment with a security story you can defend can live comfortably on Sustaining Support. And a regulated, multi-year environment is usually better served by getting back onto the standard support clock with 14c.
The mistake to avoid is letting the December 2026 date decide for you by default. Each of these tiers is a deliberate choice with a clear set of trade-offs — and the time to make it is now, while all four options are still on the table. If you'd like a second read on which tier fits your AP environment, the 12c end-of-support decision guide is the place to start, and a short Decision Call is an easy next step when you want to pressure-test the math against your own timeline.