m3ter offers two useful reconciliation features specifically designed to support AWS Marketplace integrations:
You can also exploit a general troubleshooting and reconciliation feature in m3ter, which allows you to review integrations runs performed for your AWS Marketplace Bill integrations:
When Bill-based integration runs are performed, all interactions between m3ter and AWS Marketplace are persisted as logs. These logs are retrievable via a specific API endpoint, and you can use them to track, for each Bill, all amounts sent over to AWS Marketplace, together with the date and time the Bill data was sent. This provides a report on usage data sent to AWS Marketplace for each Bill integration run, and is particularly useful for Bill recalculation scenarios where several updates might have taken place during the billing period.
API Endpoint: .../integrationdestinations/marketplace/usageReport
Example Response:
1{2"data": [3{4"accountId": "07fc9a71-74ab-492a-b6e1-f48fd8500916",5"billId": "92d3154f-4c82-40c2-9af0-5d8c14326977",6"externalSystem": "AWS",7"reportedUsage": {8"3mgmp9q6okn47u0rgmzzjdi9k-m3BillAgg1": {9"2025-06-10T10:00:00Z": 1190000,10"2025-06-10T11:00:00Z": 790000,11"2025-06-10T12:00:00Z": 54000012},13"3mgmp9q6okn47u0rgmzzjdi9k-m3BillAgg2": {14"2025-06-10T10:00:00Z": 180000,15"2025-06-10T11:00:00Z": 200000,16"2025-06-10T12:00:00Z": 200000,17"2025-06-10T13:00:00Z": 18000018}19}20}21]22}23
Note that the format of the response can vary and depends on the selected configuration option for Split usage line items - Item per bill, Item per product, or Item per aggregation.
AWS CloudTrail reconciliation is an optional feature designed to offer visibility between the data received by AWS Marketplace and the log data sent by m3ter when integrations run. The AWS Marketplace integration can then use this data comparison to help ensure billing accuracy and reliability is maintained. There are two cases where the data sent might diverge from the data received:
If the usage data sent is greater than the data received, then the integration assumes something has failed in the data sync and will automatically send the difference.
If the usage data sent is less than the data received, then the integration does not attempt to make any automatic adjustment because negative bill line items for credits are not supported in AWS Marketplace. However a safeguard is built in for this case. An alert is automatically sent to m3ter users at the end of the billing period giving details of the negative billing disparity, and enabling them to perform their own billing reconciliation, as they see fit.
By performing this compare of data sent against data received process on a daily basis, the AWS CloudTrail reconciliation feature minimizes the need for manual troubleshooting and reconciliation.
AWS CloudTrail reconciliation requires a custom event store to be provisioned on your infrastructure. An additional IAM Role also needs to be configured to allow access to that event store, with the following permissions:
cloudtrail:StartQuery
cloudtrail:GetEventDataStore
cloudtrail:GetQueryResults
The high-level process is as follows:
Daily run at 11am UTC.
Each run loads AWS CloudTrail events from the previous calendar day (00:00-24:00).
If totals match, no further action is taken.
If totals don’t match, corrective action is taken:
If the sent total is greater, corrective usage is sent over to the AWS metering API.
If the sent total is less, then an alert is issued to users.
If you've set up an integration with an external system, m3ter allows you to review details of the integration runs that have been performed for the integration. For any Bills that have been included in an AWS Marketplace integration run, you can access and review details of the run directly from the Bill details in Bill management. For example:
Select the date/timestamp hotlink text for the Last integration run to open the Integration run details page for the Bill. You can then review a Run log for the run and drill into details:
In addition to generic information on date and time of execution, and the configuration in place at that time, the Integration Run also includes full details of the payloads exchanged with AWS Marketplace.
Tip: More on Reviewing Integration Runs? See Reviewing Integration Run Details.
Next: Managing Multiple Third Party Destinations for Integrations
Login to the Support portal for additional help and to send questions to our Support team.