What’s New

We're excited to share our first changelog of the year!

Highlights from this update include:

• Expanded alert functionality for contract balance and spend threshold alerts

• New invoice breakdowns API

• Expanded business model support for recurring commits & credits, commit rates, and commit-specific overrides

• New Metronome Trust Center

• Continued Metronome 1.0 -> 2.0 parity investments

Alerts

Resolved notifications on contract balance alerts

For contract balance alerts, we now have the ability to send a “resolved” notification when the alert transitions from in-alarm to resolved. This provides an accurate, real-time indication of when customers have purchased additional credits or commits, helping to manage customer transitions between entitlement states. See docs here. If you are interested in turning on this functionality, reach out to your Metronome representative.

Custom field filters on spend threshold alerts

Alerts can be configured to track spend for contracts with a particular custom_field. This allows you to target your alerts to specific contracts or subsets of contracts. For example, you could segment your customer base into customer cohorts by labeling each contract with a custom_field, and easily implement different spend threshold alerts for each cohort. See docs here.

API investments

Invoice breakdowns

List daily or hourly breakdowns of customer invoices, optionally filtered by status, date range, and/or credit type. Invoice breakdowns provide consistent and repeatable record of customer spend, credits, and commits broken into hourly or daily buckets to help you power reliable customer-facing revenue analyses and spend dashboards. See API docs here. For more details on leveraging this data to power customer-facing dashboards, see docs here.

List balance calculation per commit or credit

The /listCustomerBalances API now returns the amount of a specific credit or commit that a customer has access to use at this moment by summing up all of the ledger entries for a commit or credit. The API allows you to easily display this information to customers, as well as facilitate downstream Finance, RevOps, and GTM workflows based on credit or commit balances. See docs here.

Uniqueness key on CreateCustomerCommit and CreateCustomerCredit APIs

/createCustomerCommit and /createCustomerCredit APIs now include the option to add a uniqueness_key to the request body to prevent creating duplicate commits or credits on retry. Request retries with a previously-consumed uniqueness key will fail with a 409 Conflict Error.

The /listCustomerCommits and /listCustomerCredits APIs also now include the uniqueness_key. See docs here.

Product custom fields in invoice and rate card APIs

Product custom fields are now available in the /getInvoice, /listInvoices, /listRateCards and /getRateSchedule API endpoints. See docs here.

Prevent updating contract end date to before end_timestamp of existing finalized invoices

In the /updateContractEndDate API, you can now set a flag to prevent you from ending the contract earlier than the end_timestamp of existing finalized usage invoices on the contract. This scenario can happen if a contract is created, a usage invoice is finalized, and the end date of the contract is later changed to end before an existing finalized invoice. See docs here.

• If you would like to prevent backdating contract end dates before finalized usage invoices, you can set allow_ending_before_finalized_invoice=false in the request body.

• In the frontend, we always allow backdating the contract end date. There is a warning in the UI: "Finalized invoices will be unchanged (void scheduled invoices to remove them, and void and regenerate usage statements to incorporate the new end date)."

Business model support

Recurring commits & credits

As part of a subscription or contract, organizations commonly allocate a fixed amount of usage to a customer. The amount generally scales with the tier of the plan, such as Good, Better, and Best. Organizations adopt this model to get the benefits of subscriptions with fixed recurring revenue and usage-based billing with collecting on overages. Model this behavior in Metronome by setting up a recurring credit or commit on a Contract.

You can create a recurring credit or commit on a Contract via the /createContract API. You can specify a recurrence period distinct from the usage statement cadence and optionally choose to prorate the first and/or last month’s commit value. Once created via API, you can view recurring credits and commits in the UI and data export. See docs here.

Commit rates and commit-specific overrides

Companies often prefer that their customers commit to spending thresholds upfront to generate more predictable revenue. To incentivize customers to do so, companies will offer discounts for larger commitments. Metronome provides the flexibility to model these discounts in two primary ways:

• Reduce the cost basis for the commit

• Create commit-specific overrides on the customer contract

For advanced billing structures, Metronome also supports a third way to discount commits: encoding commit rates on a rate card, so you don’t need to use commit-specific overrides for every customer who makes a commitment.

With Metronome’s built-in logic, you can manage both committed rates and fallback rates that kick in once the committed amount is used up—no engineering headaches required. The system automatically handles the transition to the fallback or on-demand rate, ensuring a smooth process without any manual intervention.

See docs here, and additional use-case details here.

Composite charges with >100% rate

You can set a composite charge to have a percentage rate that is greater than 100%. This change increases the flexibility of composite charges to support creative pricing and discounting schemes. Learn more about creating composite charges here.

UI improvements

Lifetime billings on the Customers list page

In our Customers list view, we now show the total lifetime billings for each individual customer. This makes it easier to find the customer you are looking for if you have multiple customers with similar names.

UI badges for customer commits and credits status

We have added badges in the UI indicating if a commit is expired, upcoming, pending, or voided. This makes the status of each commit more easily understandable in the default views. Expired commits are hidden by default, but can be exposed by selecting “Expired” within the status filter.

Security

Metronome Trust Center

Trust and security are core to our commitment to our customers. The Metronome Trust Center provides a centralized location for our latest SOC reports and information related to common questions around security.

IP Address and User Agent in Audit Logs

IP address and user agent fields are now included in audit log entries. Since this information was not previously tracked, audit logs from before 1/8/2025 will not include these two fields.

Integrations

Control service period reporting in Stripe

You can choose to have Metronome set the “Invoice Date” (also called the “effective_at” date) at the top of your Stripe invoices with the last date of the invoice’s service period. This can simplify revenue reporting processes which key off of Stripe, ensuring usage invoices are tracked against the correct period. If left unset, by default Stripe populates this date with the date the invoice is finalized. See docs here.

Data Export

Balance calculation per commit or credit

The the commits and balances tables now include a balance field, which reflects the current balance of the commit as of the time the exported report was generated.

The balance will match the sum of all ledger entries with the exception of the case where the sum of negative manual ledger entries exceeds the positive amount remaining on the commit. In that case, the balance will be 0. All manual ledger entries associated with active commit segments are included in the balance, including future-dated manual ledger entries. See docs here.

Metronome 1.0 → 2.0 parity investments

In October, we launched Metronome 2.0—a major milestone in Metronome’s mission to turn billing from a bottleneck into a growth lever. Since then, in addition to the net new feature development noted above, we have been working to complete the process of extending support for existing Metronome 1.0 features to Metronome 2.0.

AWS and Azure Marketplaces

Our native AWS and Azure integrations make it easy to use Metronome’s usage aggregation and pricing capabilities while still invoicing customers through marketplaces. In addition to setting a global billing provider per customer, billing providers can also be assigned per individual contract, providing flexibility to support multi-cloud customers. This allows you to deploy a multi-cloud commitment GTM motion, unlocking larger volumes of committed customer spend while Metronome manages the tracking of the commitment across clouds. See docs here.

International Currencies

We support 16 international currencies, providing you with a single platform that can handle usage-based billing for all of your international business lines, allowing you to move faster and simplify your billing operations. See docs here.

Invoices and usage embeddable dashboards

Embeddable dashboards allow you to embed Metronome usage data and customer invoices into your website, making it easy to integrate world-class usage and cost visibility into your product experience and increase customer trust. This is the first step to getting to parity with our plans version of this feature, so that we can build beyond it. See API docs here.

Get in touch

Enjoying our changelog? Have feedback on how we can improve it? We’d love to hear from you! To learn more about these features, get in touch with us here or reach out to your Metronome representative.