These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Cloud Cost Management
- Features
- Data operations
Data operations
Check cost ingestion, freshness, exports and integration receipts.
OverviewRejected Integration Receipts×
Cloud Cost Management · Data operations
New
Rejected Integration Receipts
Integration receipts
| Id | Provider | External event ID | Received at | Status | |
|---|---|---|---|---|---|
| IDD-366 | PRV-261 | EEI-827 | 13 Oct | Rejected | |
| IDD-750 | PRV-356 | EEI-787 | 04 Oct | Rejected | |
| IDD-277 | PRV-876 | EEI-551 | 14 Oct | Rejected | |
| IDD-964 | PRV-214 | EEI-705 | 09 Oct | Rejected | |
| IDD-105 | PRV-722 | EEI-889 | 13 Oct | Rejected |
6 of 6 records
IDD-366Integration receipts · IR-59709
RejectedProviderPRV-261
External event IDEEI-827
Received at13 Oct
What you can do
Know whether the cost evidence arrived
A spend review depends on current data. Cost ingestion runs records the pipeline, release revision, start and finish time, and outcome. Data freshness checks records when a source was checked, whether ingestion succeeded and its latency. These records help Cloud Operations Engineer answer whether a quiet day reflects lower spend or a missing feed.
Integration receipts tracks received provider events by external event ID and payload hash, with states for received, applied, rejected and failed. Billing API endpoints documents the endpoint path, method, version, service and owner. Usage windows records traffic and rejected counts for an endpoint over a defined window. Compare the receipt ID and time with the documented endpoint and run before concluding where an event stopped.
How the work is organized
- Arrival. Review pipeline runs and freshness checks for each service.
- Acceptance. Inspect receipts and rejected volume when an upstream event did not apply.
- Release. Track data exports and their validation before using an extract elsewhere.
What to agree during setup
Name each data source and the service responsible for it. Agree how late a feed may arrive before the analyst pauses a spend conclusion. Record the endpoint owner and version for billing connections. Decide what makes an export Verified, including its validation time and destination review. The team should also agree who responds to rejected receipts and how to avoid applying the same external event twice.
Start with a single provider feed. Observe a successful run, a failed run and a receipt rejected for a known reason. Make sure an analyst can tell which usage dates are complete before drawing a cost conclusion.
Check the handoff on an actual case
An analyst sees no cost lines for a service yesterday. Cloud Operations Engineer checks the ingestion run and sees it Failed, then checks the freshness record for that source. A receipt for the provider event is Rejected. The engineer checks the external event ID, endpoint version and rejected count for the matching window, then asks the billing source owner to correct delivery and checks the next ingestion run. The analyst checks that charges appear for the expected usage date before reporting a decrease in spend. If an export was already prepared, the engineer validates a new run rather than treating the earlier extract as current.
What your team sees
- Rejected Integration Receipts — Find events that need a delivery investigation.
- Spend Alert Windows — Review alert results for the affected feed period.
Follow the work through
Read data intake and spend review.
What it keeps track of
Data model- Cost ingestion runs
- Logs one run of a cost data pipeline, so the team can see if it started, finished, or failed.
- Data freshness checks
- Confirms whether a cost data source loaded on time, helping the team catch stale or broken feeds.
- Integration receipts
- Logs an event received from an external integration, so the team can confirm delivery and dedupe replays.
- Billing API endpoints
- Documents an API endpoint a service uses to pull billing data, so owners know what's being called.
- Usage windows
- Summarizes usage traffic through an endpoint over a window, flagging volume and rejected records.
- Data export runs
- Logs one export of cost data out of a store, so the team can confirm size, validity, and completion.
- Cost data streams
- Defines a live feed of cost data flowing from a source, used to configure retention and origin.
- Cost data stores
- Represents a database or warehouse holding cost data, tracked for platform and ownership.
Who uses it
Permissions- Cloud Operations Engineer
- , Cloud Cost Analyst, Admin, Service Owner.
Set up Cloud Cost Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.