Support OCI list cost ingestion separately from billed cost in Cloudability

Feature Request

Cloudability’s OCI integration appears to ingest List Cost and Billed Cost as the same value. This makes it difficult for customers to understand the difference between Oracle’s published pricing and the discounted pricing actually paid under enterprise agreements or contracted rates.

For organizations with negotiated Oracle contracts, this distinction is important. We need visibility into both:

•  List Cost — Oracle’s standard published pricing
• Billed Cost — the actual invoiced or discounted amount after contract terms are applied

Without separate ingestion of these values, Cloudability cannot accurately show:

- savings from Oracle enterprise agreements
- negotiated discount impact
- true cost optimization reporting
- variance between retail and contracted pricing

Oracle appears to provide this data through its CUR report, which seems to include Cost List information that Cloudability could potentially ingest.

Requested enhancement

Please enhance the OCI integration so Cloudability can:

1. ingest List Cost independently from Billed Cost
2. preserve both values as separate fields in reporting
3. expose the delta/savings between list and billed costs
4. allow customers to report on Oracle contract savings over time

Business impact

This capability would help enterprises:

- quantify savings achieved through Oracle contracts
- improve financial transparency for OCI spend
- support internal FinOps and procurement reporting
- better validate the value of negotiated pricing agreements

Suggested implementation note

If Oracle’s CUR already includes a Cost List field, Cloudability may be able to use that source directly rather than deriving list pricing indirectly.