Savings receipt export
Baseline, observed cost, checkpoints, confidence and methodology for one action.
Evidence
CSV and JSON export workflows for savings receipts, finance reporting and evidence sharing.
Baseline, observed cost, checkpoints, confidence and methodology for one action.
Verified, pending, regressed and inconclusive savings across approved actions.
State-changing operations with actor, correlation ID, timestamp and result metadata.
Normalized multi-cloud inventory with provider metadata and scope identifiers.
Evidence references linked to action executions, receipts and review workflows.
01
Choose scope
Pick a receipt, verified savings window, provider, scope, status or reporting period.
02
Generate file
Small exports return directly; larger bundles run as background jobs and appear in export history.
03
Validate contents
Check row counts, timestamps, filters and checksum metadata before sending outside the team.
04
Hand off evidence
Share the export with finance, auditors or stakeholders together with the request context and reporting period.
| Export | Important fields |
|---|---|
| Savings receipt | baselineId, actionRequestId, baselineDailyUsd, checkpoints, confidence |
| Verified savings | verifiedSavingsUsd, latestStatus, capturedAt, daysObserved, resourceId |
| Audit logs | actor, action, target, result, correlationId, createdAt |
| Resources | provider, region, type, scopeId, tags, metadata, lastSeenAt |
| Evidence | artifactType, source, checksum, generatedBy, generatedAt |
Exports are always tenant-scoped by organization context.
Asynchronous export jobs are metered and can be plan-gated.
Receipt and evidence exports should be validated before finance or auditor sharing.
Use consistent reporting windows for trend comparisons.
Next: check export entitlements in Plans & Features or review the sample savings receipt. For compliance packages, create an audit bundle.
Connect one AWS, Azure or GCP scope, approve the safest savings actions, and give finance a receipt when the savings verify.