Billing & Reports
A Billing Summary reports what your organization spent in a period, broken down by workspace, project, or member. Every row exports a detailed CSV carrying the individual charges behind the total, which is where you reconcile a line item back to the job that generated it.
Viewing billing summaries
Billing Summaries live in either administration portal under Financials > Billing Summaries. Both portals offer the same view, and what differs is the scope of the data in it. An organization administrator sees usage for the whole organization and can break it down by workspace, project or member. A workspace administrator sees usage for their own workspace and can break it down by project or member.
The default view covers the current month, and you can go back as far as thirty-six months. The By dropdown changes the level the summary is broken down to, and the period filters beside it set the range of months you want to see.
Billing Summaries and Billing CSVs report in UTC. Month boundaries in these reports align to UTC, not to your local time zone.
Reading a billing summary
Each row aggregates charges at whichever level you chose in the By dropdown, so a row represents an organization, a workspace, a project or a single member. The columns are the same in every case.
Summaries from earlier periods use a simpler breakdown, with Hardware, Software, Storage, Transfer and Connections columns alongside a single Deposits and Credits column. In that older view each deposit applies against future consumption, which is why the Credits column shows a negative entry equal to that period's charges, and why the Total column reflects what you actually paid rather than what was incurred.
Downloading the billing CSV
Every summary row carries a Download button that exports a detailed Billing CSV for that row's scope. The CSV is the authoritative record of the individual charges that roll up into the aggregates on the summary page, and a single download can cover up to twelve consecutive months.
The CSV carries the following columns.
Billing CSV data precision
Prices are set to four decimal places, and charges are calculated at that precision before being rounded for billing. Rounding is always up, and the rounded figure is what appears in the CSV:
The same rule applies on every platform.
Understanding storage billing
Storage is billed on your average storage usage for the month, not your peak. Rescale calculates the average by summing the total size of every file that was available to you during the month, weighted by the time it was available.
Key rules:
- Month boundaries are UTC.
- Sizes are binary. 1 GB means 1 GiB (1,024 MiB) and 1 TB means 1 TiB, both in the size Rescale reports and in the figure you are billed on.
- The minimum billable unit is 1 GB. If any file was present during the month, you are charged for at least 1 GB.
- If a file is uploaded mid-month or deleted before the end of the month, its contribution is prorated.
- Archived and trashed files still count. A file contributes until it is permanently deleted — see the file lifecycle.
Because the charge is weighted by time, when you delete something matters as much as what you delete. Purging a large result set early in the month cuts its contribution proportionally, whereas leaving the same data in the trash for three weeks means paying for three weeks of it.
To see current per-user consumption rather than last month's bill, use monitor storage and transfer usage.
A single file present for part of the month
Suppose you upload a 60 GB file on the 5th of a thirty-day month and delete it ten days later. Because it was available for ten of the thirty days, it contributes a third of its size to the month's average: 60 GB * 10 days / 30 days = 20 GB.
Overlapping files, across two months
Now take three files with overlapping lifetimes. An 80 GB file is uploaded on March 20 and is still present through April and May. A 30 GB file is uploaded on April 10 at 14:10 and deleted the following day at 13:15. A 25 GB file is uploaded on April 25 at 18:00 and deleted on May 28 at 18:00.
For April (30 days = 43,200 minutes), the average is (80 * 43,200 + 30 * 1,385 + 25 * 7,550) / 43,200 = 85.33 GB.
For May (31 days = 44,640 minutes), the 25 GB file is available from the start of the month until the 28th at 18:00, which is 39,960 minutes: (80 * 44,640 + 25 * 39,960) / 44,640 = 102.38 GB.
A short-lived spike costs almost nothing
You start June with 99 GB of files, then a job generates 902 GB of output.
Nine times your baseline, present for less than an hour, moves the monthly average by roughly 1 GB. The point to take from this works in the other direction too: a large output set left in place for weeks raises the average far more than the same data generated and cleared quickly, so what matters is how long data sits rather than how much of it arrives.
When different charges appear in billing
Not every charge is generated on the same schedule. Compute charges appear while a job is still running, while connection charges are not generated until the month closes. If a charge you expect is missing, this table is usually the reason.
The same rules apply whether you read the data in the UI or pull it through the API.
Which charges roll up to each Rescale service
A single workload generates several separate charges, which is why a line item in the CSV rarely accounts for the whole cost of the thing that produced it. When you are reconciling a charge back to a workload, this table gives you the full set to look for.
The Financials tab
Both admin portals have a Financials tab, and both show the same views. What differs is the scope of the data in them: an organization admin sees every workspace in the organization, and a workspace admin sees only their own workspace.
Invoices
The Invoices view lists invoices across all workspaces by default, and the dropdown on the right filters it to a single workspace. Where a month contains several invoices, they are grouped together under that month.
Purchase orders
Purchase orders are listed across all workspaces alongside the Workspace ID each belongs to, and the view can be filtered per workspace in the same way.
Beneath them, a Negative Balance section totals negative balances across the organization by month. These represent charges that no purchase order covers. If you run a PO-based approval process, this is the figure to watch, because it is the gap between what has been consumed and what has been authorized.
Credits
Every credit on your organization is listed with its type, the workspace it belongs to, the original amount and how much remains. Each row also records when the credit was added and which Rescale user added it, which is what you quote if you need to query one.
A software credit additionally names the software it covers, because a credit restricted to particular applications cannot pay for anything else.
AWS Credit Transfer
If your organization holds AWS credits, admins can request they be transferred to Rescale to fund AWS infrastructure consumed through the platform. Only available to organizations using AWS credits.
Deposits
Deposits appear here too, with the same fields documented in deposit types. Note two easily-confused columns:
"Remaining" is the number that tells you what's actually left.
How a deposit differs from a budget
A deposit is money. Your organization pays Rescale, an ISV, or a partner in advance, and the resulting balance is what settles your charges as you consume them. When the balance runs out, there is nothing left to pay with.
A budget is a limit. It caps how much a member, project, or workspace is allowed to spend, and it settles nothing at all. When a budget is reached, the money may still be sitting in your deposit, but the team is no longer permitted to draw on it.
Because they do different jobs, having one without the other rarely works. A budget with no deposit behind it stops work without ever having paid for anything. A deposit with no budget pays for whatever anyone chooses to run. Most organizations set both, and a job has to satisfy both before it launches.
For how the caps themselves behave, see how budgets work.
Related
- Budgets & Deposits for prepaid credits and spend guardrails that these reports reconcile against.
- Usage Dashboards for the Economics and Utilization dashboards, and individual account usage.
- Commitment Plans for where the Applied Commitment line comes from.