How to Track OCI Costs Across Multiple Tenancies
If you manage more than one Oracle Cloud tenancy, you already know the pain: each customer or business unit has its own OCI Console, its own billing view, and its own set of compartments nobody outside that team understands. Finance asks for a consolidated spend report. A customer disputes a line item. Your engineers need to know whether a spike came from compute, block storage, or Autonomous Database - and they need the answer today, not after three days of console hopping.
Tracking OCI costs across multiple tenancies is a governance problem as much as a finance one. This guide covers the practical approaches MSPs and enterprise cloud teams use to get accurate, comparable cost visibility - and how OCI Vision's Cost section brings multi-tenancy cost analysis into a single workspace.
Why the OCI Console alone is not enough
Oracle Cloud provides cost analysis tools inside each tenancy, but they are scoped to that tenancy only. An MSP managing twelve customer estates must log into twelve consoles, export twelve CSV files, and manually merge them in a spreadsheet before anyone can answer a simple question like "which customer spent the most on Object Storage last month?"
Enterprise teams with a single large tenancy face a different version of the same problem: cost data is fragmented by compartment and region, and finance rarely has IAM access to every compartment that engineering owns. Without a centralised view, cloud spend reviews become a recurring fire drill rather than a routine governance activity.
The OCI Usage API solves the data access problem - it returns granular usage and cost records programmatically - but you still need a tool that aggregates results across tenancies, normalises the output, and presents it in a format your team can actually use. That is where a purpose-built cloud governance platform earns its keep.
Group costs by service, compartment, or region
Raw cost totals are rarely enough. The first question after "how much did we spend?" is almost always "on what?" OCI Vision's Cost section lets you pivot spend data by service, compartment, compartment path, region, resource, resource name, or SKU - so you can slice the same dataset differently depending on who is asking.
Group by service is the default starting point for most reviews. It answers whether compute, block volumes, networking, or database services drove the bill - essential when a customer asks why their monthly invoice jumped 40%.
Group by compartment maps spend to organisational structure. MSPs use this to show each customer exactly what their tenancy compartments consumed. Enterprise teams use it to attribute costs to application teams, environments, or cost centres without relying on tag hygiene alone.
Group by region reveals geographic distribution of spend. Multi-region estates often have unexpected cost concentration in a secondary region where a DR environment quietly accumulated orphaned resources. Region-level grouping surfaces those patterns quickly.
Switching between group-by dimensions without re-querying OCI manually is one of the biggest time savings over spreadsheet-based workflows. The cost pivot table in OCI Vision renders dates as columns and your chosen dimension as rows, with column totals and a grand total - the same layout finance teams expect from enterprise reporting tools.
Stacked charts and flexible date ranges
Numbers in a table tell you what happened. Charts tell you when and how fast. OCI Vision renders stacked bar charts from Usage API data, with each series representing a service, compartment, or whichever dimension you selected. Toggle between daily bar view and cumulative mode to see whether spend accelerated mid-period or accumulated steadily.
Date range selection matters because OCI billing cycles and customer contracts rarely align with calendar months. Pick a custom start and end date to match a customer's billing window, a project phase, or a quarter-end close. The summary header shows cost to date for the selected period alongside an optional forecast when the end date extends into the current month.
Forecast days are marked on the chart so stakeholders can distinguish actual usage from projected spend - useful during mid-month customer reviews.
Compare tenancies side by side for MSPs
MSPs live and die by their ability to report accurately per customer. OCI Vision connects multiple tenancy profiles within a single organisation workspace, then aggregates cost analysis across all of them. Filter to one customer tenancy for a focused review, or leave the filter on "all" to compare estates at portfolio level.
Each tenancy profile uses its own encrypted credentials and scans independently. If one customer's Usage API credentials are misconfigured, the other tenancies still return data - errors are reported per profile rather than failing the entire report. This isolation model mirrors how MSPs should structure customer access in OCI itself: separate credentials, separate scopes, shared reporting layer.
Pair cost data with inventory from the same platform and you get context spreadsheets cannot provide. When a customer's compute spend spikes, jump to the Compute section and see exactly which instances changed.
Export cost PDFs from Reporting Studio
Internal dashboards are useful, but customers and auditors want documents they can file. OCI Vision's Cost section includes a one-click cost PDF export that captures the chart, pivot table, period summary, and currency totals in a formatted report suitable for customer billing reviews, internal finance packs, or quarterly governance meetings.
The PDF footnote clarifies that figures come from the OCI Usage API and may differ slightly from invoice totals due to rounding, credits, or delayed usage data.
Configure read-only Usage API permissions
Cost analysis requires access to the OCI Usage API, which is separate from standard resource read permissions. Your dedicated read-only IAM user needs an explicit policy statement:
Allow group oci-vision-readers to read usage-report in tenancy
This is a read-only permission - it grants visibility into usage and cost records without any ability to create, modify, or delete resources. The Usage API must be called from the tenancy home region, which OCI Vision handles automatically during collection.
Never use tenancy administrator credentials for cost reporting tools. Admin keys carry full manage permissions across every resource in the estate. If those credentials are stored in a third-party platform and later compromised, the blast radius includes every customer workload - not just billing data. A dedicated read-only service user with compartment scoping where appropriate follows least-privilege principles that auditors expect.
OCI Vision stores credentials encrypted at the organisation level and requires confirmation that each profile uses a read-only IAM user before saving.
Bring cost tracking into your governance workflow
Cost visibility should not sit in isolation from inventory, IAM, and compliance data. When spend anomalies appear, the next step is almost always an operational investigation: what resources exist, who owns them, and whether they comply with policy. A cloud governance platform that combines cost analysis with live inventory, IAM visibility, and audit-ready PDF exports turns monthly billing reviews into a continuous governance loop rather than a quarterly scramble.
OCI Vision gives MSPs and cloud teams multi-tenancy cost pivots, stacked charts with flexible date ranges, tenancy comparison across organisation workspaces, and formatted cost PDFs - all powered by the OCI Usage API through read-only credentials you control.