• Home

Changelog

This changelog lists the new features, functionality, and updates added in each month for 2025.

Version: October 2025

New Features

• Usage Data Explorer The new Usage Data Explorer (v2) is now Generally Available. The old Usage Data Explorer will continue to be available until March 2027 (see "Upcoming Changes" below).

• Bill Statements. Line Items now include the relevant contractId for any corresponding source Bill line items that are linked to a Contract.

• Data Exports. Data Export jobs now emit a dataexport.job.success Event after completing successfully.

• Meter Derived Fields. Derived Field calculations can now reference the account code directly as m3ter.account.code.

Console Improvements

• Product details. You can now quickly review and manage the entities created for a Product on the Product details page. Separate tabs are provided for each entity type and you can open the details page for a specific Product entity directly, as well as edit or delete entities.

• Bill management. Usability enhancements:

  • Your invoice date range selection on Bill Management is now saved in the query string so reloading or going back retains your selection.

  • Filtering Bills is now more intuitive with radio button options to filter quickly for Approved or Pending status or by switching to show only Locked Bills.

• Account pages:

  • If an Account Plan has had a Billing cycle date defined or has been added to a Contract on the Account, then the Attached Plans tab now clearly shows this.

  • Account details are now only shown on an Account's Overview tab leaving more room when working in other tabs.

• Entity metadata. The metadata cards on details pages now list the latest integration runs for relevant entity types and users can use a link to view all runs.

• Create and Edit Forms. When users have made editing changes to Create or Edit forms and then attempt to navigate away, a helpful dialog now appears to remind them that there are unsaved changes and asking them to confirm they want to leave the form without saving.

Changes and Bug Fixes

• Fix: An issue where the Balance details page attempted to load too many Bills has been resolved.

• Fix: Some character sets were not rendered correctly on Console screens. This issue has now been resolved.

Upcoming Changes

• Usage Data Explorer (v1). With the release of the new Usage Data Explorer, we're starting the process of retiring the legacy version. Your m3ter contact will reach out with more details and assistance on migrating. The following key dates should be noted:

  • 1st March 2026: Usage Data Explorer v1 will enter maintenance mode. After this date, it won't receive new features or enhancements, but will continue to receive security updates.

    New customers onboarded after this date will only have access to the new version.

  • 1st March 2027: Usage Data Explorer v1 endpoints will be removed.

• New API infrastructure. We’re preparing to migrate the m3ter APIs to new infrastructure. This change will be transparent to RFC-compliant clients, but the new infrastructure is less tolerant of non-RFC compliant requests. We’re reaching out to customers we can know will be affected, and will confirm a timeline for the change in due course, but in the meantime customers should check they are adhering to the following:

  • All requests with a body need to include the appropriate Content-Type header, typically content-type: application/json.

  • Requests using HTTP methods that do not expect a body, such as GET, HEAD, and OPTIONS, must not contain one.

• HTTP status codes for oversized payload. In December, we'll be making a change to give a different and more informative 413 error code when the payload in a PUT request to our APIs is too large.

• Bill Statements. In December, we'll be making a change to what Statement line items are generated for Bills in some specific configurations. After the change, a Statement line item will be produced for each Meter referenced by a Compound Aggregation, rather than a single Statement line item per Compound Aggregation. This will ensure any usage filters applied for the Statement don't risk usage being omitted at Statement generation.

  You will only be affected by this change if:

  • The pricing uses a Compound Aggregation, and the Compound Aggregation references multiple Meters.

  • The Statement Definition uses a field as a dimension that exists in some, but not all, of the Meters used.

• Bill Statements. In December, we'll be changing the way Statements are generated for Bills resulting from segmented pricing. If a segment pricing is updated, any Statements generated after the update will not include the pricing bands for the earlier legacy segment pricing.

• Credit Charge Amounts with Parent/Child Accounts. Where the billing mode is set to bill the Parent Account, and Account Plans are attached only to Child Accounts, in December a change will be made to allow credit charge amounts to be recognized for Parent Account billing. Previously in these scenarios only debit charge amounts were recognized for Parent Account billing.

• We reported last month that the Retrieve Line Item Usage in JSON Format endpoint had been deprecated and will be removed in November 2025. The associated jsonUsageGenerated response parameter for the List Line Items endpoint has been deprecated and will also be removed.

Version: September 2025

Product Updates

Azure Marketplace Integration

A new Azure Marketplace native integration is now available in Beta release version, which you can use to send your end customer Account Bills generated in m3ter into Azure Marketplace. Included with this release is a reconciliation feature designed to support your Azure Marketplace integrations:

• Billing usage data reporting. Performed for each integration run and allows you to track all amounts sent over to Azure Marketplace for each Bill, together with the date and time the Bill data was sent. This is particularly useful for Bill recalculation scenarios where several updates might have taken place during the billing period.

Data Exports

• Scheduling. When setting up a Schedule, you can now use a simple or advanced mode for defining when exports will run:

  • Simple Scheduling. Define a frequency in days, hours, or minutes. For daily and hourly scheduling an offset is now also available. For daily jobs, you can offset in hours from midnight. For hourly jobs, you can offset in minutes from the start of the hour.

  • Advanced Scheduling. Define when exports run using the cron format.

• Operational Data Exports. Charges are now available in operational Data Exports.

• See Data Exports.

Usability Improvements

• Calculation Editors. Several usability enhancements:

  • Referencing Custom Fields in Derived Field editor. Includes autocomplete/tooltips for defined Custom Fields. As you start to enter a field in the editor:

    • A list of any matching defined fields shows with prefix allowing you to read-off whether field is defined at Organization or individual entity level.

    • Context-sensitive filtering is applied - if a Meter is Product linked, then only Product Custom Fields are shown.

  • All Calculation Contexts:

    • Context-sensitive tooltips for functions showing syntax and examples.

    • Support for IF..THEN..ELSE syntax, so you can use that instead of ternary expressions for more readable calculations.

    • Clickable link to open calculation engine reference documentation.

• Organization Selector. Organization type is now more clearly and readily indicated for users both when changing Organization and when working in the Console:

  • Production Organizations are labeled in red.

  • Sandbox Organizations are labeled in teal.

• Page Not Found. User experience has been significantly improved for when a Page Not Found error occurs. The m3ter branding and page header is now always shown together with a more helpful message and link to the Dashboard. If you're logged in, you also get your user actions and the main navigation to help you quickly get back on track.

Coming soon

• In December 2025, we’ll be introducing validation that the ets timestamp optionally present in usage data measurements must be equal to or after the ts timestamp. Measurements that fail this validation will be rejected using the standard method for the method of ingest being used.

• Bill Statement line items will soon have the relevant contractId added to them for any corresponding source Bill line items that are linked to a Contract.

• The previously deprecated configData request parameter for the Create Account endpoint will be removed in November 2025.

• The Retrieve Line Item Usage in JSON Format endpoint has been deprecated and will be removed in November 2025.

• The Count Notifications endpoint has been deprecated and will be removed in November 2025.

Version: August 2025

Product Updates

• Meters. Product-linked Meters can now be made into Global Meters.

• Calculation Functions. A new IN() function is available which takes multiple arguments. Can be used with the ternary operator to return TRUE if any of the arguments are satisfied, otherwise return FALSE:

  • For example, IN("completed", "succeeded") ? "true" : "false

• Permission Policies. New export:config resources and an export:download action are now available for creating a custom Permission Policy granting Users full working access to create, manage, and run data exports.

• Balances. Custom Fields can now be added to Balances at the individual entity level.

• Data Exports. Accounting Product fields for Bill line items are now included in Data Exports.

• m3ter SDKs and Terraform Provider. New versions of the m3ter SDKs and Terraform provider have been released with various fixes and enhancements. See Developer Tools for details.

• AWS Marketplace Integration. The m3ter platform integration is now listed on AWS Marketplace. You can review our blog posting for more details.

API Updates

• User:

  • A new Retrieve current user information endpoint was added to the API and SDKs. This allows you to identify and check the current session's user.

Console Updates

Usability Improvements:

• Integrations. On the main Integrations page, the badges for external systems now show the number of Credentials and Configurations set up for a system. If either a Credential is disconnected or a Configuration is disabled, then a warning will show.

• Plan Templates. You can now price a Plan Template directly from the Plan Template details page.

Resolved Issues

• Fix: Previously a Balance could be created for an Account without specifying a Name or Code. This is no longer possible and any Balances created without Name or Code will now be required to add a Code when updated.

• Fix: If a Create or Edit form was opened in a new browser tab, the Cancel button was inactive. This has now been resolved.

Version: July 2025

Product Updates

• Events and Notifications. New system Events are generated for Balance amounts - when a Balance amount is created, updated, or deleted. Notifications based on these Balance amount Events can be set up to meet common use cases, such as an alert when a Balance amount reaches zero, is consumed down a preset threshold, or is consumed down to a defined percentage of the initial amount.

• Accounting Products for Bill line items:

  • Reviewing Bills. If you've defined Accounting products for line item types to meet your revenue recognition and accounting purposes, when reviewing and managing Bills in Bill management you can now group line items by Accounting product.

  • Integrations. If you've set up a billing integration with your external accounts receivable and invoicing system, the integration will now use the Accounting product ids assigned to line items.

• Terraform Provider. The m3ter Terraform provider joins our SDKs in developer tools and is available for early access use, allowing you to manage m3ter resources using the popular infrastructure as code tool from Hashicorp. See Developer Tools for details.

• Integrations. When configuring billing integrations with your external systems, you can now filter the line items included in the integration using line item Product IDs or Aggregation IDs.

API Updates

• Marketplace Integrations:

  • A new Retrieve reported usage endpoint is available, which allows you to return a list of reported usage records for integration runs with external marketplace systems. Query parameters are available to filter what is returned in this usage report by billStartDate, billId, externalSystem, or accountId.

Console Updates

Usability Improvements:

• Account Plan and Plan Group attachment:

  • Plan details. When reviewing an Account's Plan attachment details, a new hotlink text allows you to open the Plan attached to the Account directly.

  • Attached Plan pricing. The pricing for an attached Plan is now shown in the same panel as the attached Plan's details, make it quite clear the pricing is associated with the Plan. Similarly for when a specific Plan in an attached Plan Group is selected - the associated pricing is shown with the Plan details.

  • Plan Group attachment. When a Plan Group containing many Plans is attached to an Account, the attachment page loading is much faster.

• Accounts section. The Accounts section of the Console now provides a faster loading experience and when opening the details pages for entities attached to an Account a full breadcrumb trail is given.

Resolved Issues

• Fix: Previously, the Console usage data ingest form could be submitted when invalid JSON was shown, and the last valid JSON entered was submitted without any indication to users. This issue is now resolved.

• Fix: The usage chart for latest bills on the Account Overview tab now correctly includes for any billed usage with a service period of one day or less.

• Fix: An issue that allowed invalid Custom Fields to be attached to a Contract has now been resolved.

• Fix: The Hide zero quantity line items display option available when viewing Bills containing zero line items is now working correctly to hide any and only the zero quantity items.

• Fix: An issue has now been resolved that prevented an Aggregation being used to price a Plan in a Plan Group if the Aggregation had been used to price another Plan in the same Plan Group.

Version: June 2025

Product Updates

• Account Balances linked to Contracts. Account Balances can now be optionally linked to a Contract on the Account. If you've linked an Account Plan to a Contract, link a Balance to the same Contract to ensure the Balance is available for draw-down. See Linking Balances to Contracts for more details.

• Integrations A new AWS Marketplace native integration is now available in Beta release version, which you can use to send your end customer Account Bills generated in m3ter into AWS Marketplace. Included with this release are two reconciliation features specifically designed to support AWS Marketplace integrations:

  • Billing usage data reporting. Performed for each integration run and allows you to track all amounts sent over to AWS Marketplace for each Bill, together with the date and time the Bill data was sent. This is particularly useful for Bill recalculation scenarios where several updates might have taken place during the billing period.

  • AWS CloudTrail reconciliation. Provides visibility between the data received by AWS Marketplace and the log data sent by m3ter when integrations run. This data comparison is then used to maintain data parity between systems by identifying differences and automatically making adjustments to reported metering data, and removes the need to carry out manual troubleshooting and reconciliation for clean billing operations.

  • See Configuring AWS Marketplace Integrations for more details.

• Custom Fields:

  • Balances. You can now add Custom Fields to Balances at the individual entity level. See Creating a Balance on an Account for more details.

  • Balance Schedules. When setting up Transaction or Charge Schedules for Balances, you can now add Custom Fields to them. See Creating Transaction Schedules for Balances and Creating Balances Charge Schedules for more details.

• Data Exports. Transaction Types are now available for operational Data Exports.

• Calculation Functions:

  • Date Time Functions. The new DateTime.secondsOverlap function allows you to calculate the total number of seconds of overlap between a given overall time range and a time period. This function is useful in cases where discount rates are offered for service consumption during "off-peak" hours - for example any consumption on any given day that is outside the peak rate hours of 06:00:00 until 22:00:00. See Date Time Functions for more details.

  • Math Functions. For the Math.ceil(), Math.floor(), and Math.round() functions, a second optional parameter is now available to control the scale of the result. See Functions for more details.

Console Updates

Usability Improvements:

• Code Editor. Several usability enhancements: consistent highlighting; auto-adjustment in size to full width in read and edit mode and to accommodate multi-line calculations; clickable suggestions to expand for fuller descriptions.

• Ad-hoc Operational Data Exports. Help texts for the Time period options have been updated to make clear that the export will include operational data from a defined start date/time up until when the export runs, and not a defined end date/time.

• Entity Metadata for Custom Fields. When reviewing the Metadata panel for an entity, any Custom Fields configured at Organization level for that entity type are shown together with their values, which can be copied. If a corresponding Custom Field has been created for the individual entity, then the value defined at Organization level is struck through to clearly indicate that the individual entity level value will be used.

• Balance Transactions. The Balance Transaction table on the Balance details page can now be sorted ASC/DESC by column.

• Meter Details. Data fields for Meters are now clearly grouped on the Meter details page: Measure data fields, Dimension data fields, and Derived fields.

Usage Submissions:

• End Timestamp. When submitting usage data measurements into the Ingest API from either the Meter details or Account details pages in the Console, you can now enter an optional End timestamp date/time for the submitted measurement.

• Submission Activity. The Activity panel on the Meter details page which tracks usage data submissions for the previous hour has been optimized for faster response times and refresh rate as you submit measurements.

Balance Details. The Balance details page now contains three additional summary fields tracking key amounts in a Balance's lifecycle: Balance consumed, Rollover consumed, and Expired Balance amount.

API Updates

• Integrations - Retrieve Available endpoints updates:

  • Retrieve Available Configurations. This endpoint now supports two optional query parameters for systemName and entityType. When these are used, the response contains a new selectedConfigurations section.

  • Retrieve Available Integration Systems. New endpoint and supports an optional entityType query parameter.

  • Retrieve Available Entity Types for System. New endpoint and returns the available entityTypes for the given system.

  • Retrieve Available Auth Config for System and Entity Type. New endpoint and returns the auth configuration for the given system and entityType.

Resolved Issues

• Fix: The Timestamp column in the Result rows table of Usage Data Explorer (v2) now correctly displays a UTC date/time.

• Fix: An issue where the Balance Transactions ledger was not correctly tracking Transactions has been resolved.

• Fix: When editing a Google Cloud Platform Destination for Data Exports, an issue where the incorrect edit form showed is now resolved.

• Fix: Some searchable drop-down selection lists showed incorrect filtering on text entry. This has now been resolved.

• Fix: The Custom Fields section on the Bill details Metadata panel has now been removed since not applicable.

• Fix: When editing External mappings an issue where the linked integration was not showing on the Edit form has been resolved.

Version: May 2025

Product Updates

• Billing Operations - Line Item Usage Insights. When reviewing a Bill's details, you can now drill into usage line items and quickly gather key information about the usage directly and without having to move to other areas of the Console to obtain a fuller picture the billed usage:

  • The Meter and pricing components - Aggregation, Plan, and Pricing - are identified with hotlinks to open their details pages.

  • A bar chart displays the distribution of usage across the relevant bill period and spikes in usage can be readily identified.

  • A download button is provided to obtain a CSV formatted file of the line item's usage.

  • If any further investigation is required, open the Usage Data Explorer directly with a query to return the line item's usage preloaded and performed.

• Date Time Functions. New date time functions have been added to the m3ter Calculation Engine and are now available for use in Derived Field, Compound Aggregation, and Notification Rule calculations. Please see Date Time Functions for details.

• Data Exports:

  • Usage Data Exports now use Data Explorer v2 queries to return usage data for export. You can open Data Explorer v2, build a query, and check the usage data returned. If satisfied, you can then quickly load the query into the Data Export page and complete setting up a usage data Export Schedule or Ad-Hoc Export.

  • The frequency for Export schedules can now be set at minute intervals as well as at hourly or daily intervals, with a highest frequency limit of every 15 minutes.

  • Setting the time period for Ad-Hoc Operational Exports has been simplified and requires users to specify only a start date/time. The Export will include only the operational data created or modified from the specified start date/time up until when the Export runs.

• Account Contracts. Custom Fields can now be created for Contracts at the Organizational level as well as individual Contract level. This means Contract Custom Field values are available for calculations.

Console Updates

Usability Improvements:

• Notification/Webhook Links. The links between Notification Rules and Outgoing Webhooks which support Notification Webhook integrations can now be much more easily managed through a new link details modal. This intuitive screen can be quickly accessed from either the Notification Rule or Outgoing Webhook details page, allowing the active/inactive status of the Notification Webhook integration to be checked and managed or Organization users to be added for receiving email notices when the integration has been auto-disabled. See Linking Notifications to Outgoing Webhooks for details.

• Meter Derived Field Calculations - Editor. When creating and editing Derived Field calculations, the Derived Field ordering can be quickly changed to facilitate referencing Derived Fields earlier in the list, and the calculation editor now provides completion suggestions and syntax highlighting.

• Currencies. A new separate Currency settings page is now available, making creation and management of currencies and currency conversion rates in your Organization easier and more accessible. See Creating and Managing Currencies for details.

• Balances:

  • The Balance summary listing page for an Account now has a Currency column.

  • The Transaction ledger for a Balance now shows "Billed" not "Paid" against Transaction amounts to avoid any suggestion that m3ter provides a collections or payments function for end-customer Account Balances.

  • When creating or editing a Transaction for a Balance in the Console, users can now define the Transaction date and Applied date.

• Data Exports. Console pages and forms for configuring and managing Data Exports now all consistently use UTC for date/times, with clear labeling to avoid any user uncertainty.

• Integrations:

  • The Credential being used to connect an integration with an external system is now clearly shown on the Integration details panel.

  • The Integration runs page listing can now be filtered by run status and sorted by run start time.

API Updates

• The Get Balance Transaction Summary endpoint in the Config API now provides three extra response parameters giving amounts for expiredBalanceAmount, rolloverConsumed, and balanceConsumed.

Resolved Issues

• Fix: Issues where several configuration forms were missing Accounting product settings have now been resolved.

• Fix: When creating Charges for Accounts, it was possible to set an end date for a Charge that was before the start date. Extra validation is now in place to prevent this.

• Fix: An issue has been resolved where Events associated with Custom Fields and segmented Aggregations were being stored in an inconsistent way making the data inaccessible when transferred into Notification payloads. For example:

...

"segments": "[{country=PT}, {country=ES}, {country=UK}, {country=EE}, {country=IE}, {}]",

...

• The content for the affected Events is now structured in an accessible format and consistent with the standard API response formatting:

"segments" : [

{

"country" : "PT"

},

{

"country" : "ES"

},

....

• If you suspect this issue has affected you, please get in touch with your m3ter contact or contact m3ter Support.

Version: April 2025

Product Updates

• Charges on Accounts. You can now create Charges for your end-customer Accounts to serve use cases that require ad-hoc or one-off line items for Account billing. Charges are:

  • Created for either debit or credit amounts and are available in any currency defined for your Organization.

  • Assigned a service period and given a specific date for billing the Account. When a bill job has run for the specified bill date, the Charge appears as an Ad-hoc line item on the Bill.

  • Linked to a Product for accounting purposes and can be optionally linked to a Contract.

  • See Creating Charges for Accounts for more details.

• Integrations. A new NetSuite Notification native integration is now available in Preview release version, which offers wide flexibility for controlling when the integration runs and for controlling what range of m3ter entity data is sent through to your NetSuite system. The integration:

  • Exploits m3ter's Notification framework driven by system Events, which means you can specify one or more Notifications that will trigger the integration. The integration runs when the relevant system Event occurs and triggers the Notification rule.

  • Links to a Transformation you've set up in m3ter. By defining a one-way data mapping from one specific data type to another, Transformations allow you to customize the conversion of data as it flows into or out of the m3ter system via integrations.

  • See Configuring NetSuite Notification Integrations for details.

• m3ter SDKs. SDKs are now available in Alpha for Python, Golang, and TypeScript/Javascript. See m3ter SDKs for details.

• Data Exports:

  • Destinations. You can now export your m3ter usage and operational data to Google Cloud Storage bucket destinations.

  • Usage Data Export. The capabilities of the new Usage Data Explorer (v2) for querying usage data are now fully available to the Data Export service, offering you significantly more power and flexibility to control precisely the range of exported usage data.

Console Updates

Usability Improvements:

• Advanced Account Browsing. The Accounts page now offers a range of new features:

  • Sorting added, with intuitive default sort order when the page is first opened.

  • Additional columns can be added to the listing and the ordering of columns changed to suit user requirements.

  • Advanced search and filtering, with shareable URLs when search filters applied.

  • General usability enhancements:

    • Anchored pagination controls avoiding the need to scroll to use.

    • Improved empty/no results state.

    • Loading spinner not present when returning from an Account details page.

• Select modal listings. Modal selection views have been recast to improve usability, including:

  • Anchoring the pagination controls at the bottom.

  • The number of selections made is dynamically tracked.

• Delete confirmations. When deleting entities, the confirmation dialog now states explicitly the entity selected for deletion.

• Integration Details. The integration details page has been updated to make adding and managing Credentials for an integration easier with added Credentials clearly listed.

Version: March 2025

Product Updates

Usage Data Explorer V2. A new version of Usage Data Explorer is now available in Preview release, which you can use to query the metered usage data collected for your Organization in m3ter. The Console user experience is highly intuitive and facilitates setting up a query that returns the precise usage data set needed to serve your current analytical purposes. Features include:

• Dimensions filtering. Filter the usage data returned by specific Dimension data field values.

• Aggregate data. Apply Aggregation functions to the usage data returned for the query.

• Grouped by. For queries that apply Aggregations, select to group the data returned for the query by:

  • Account

  • Time

  • Dimension

• Reviewing query results. Review the data returned for your query in a Results row table.

• Query saving and re-loading. Quickly save a query and re-use it.

• Downloading query results. From the results table, promptly download the returned data set in a CSV or JSONL formatted file.

Data Exports Service:

• Downloads to Local Device. Now available through the Console. If you omit a Destination for either an Export schedule or an ad-hoc Export, when the Export job runs and has succeeded a file download button is provided on the Export jobs page.

Console Updates

Usability Improvements:

• Calculation Editor. The display and editing experience for creating calculations in the Console has been greatly enhanced. This includes full syntax highlighting support for the m3ter calculation language and other editing features:

  • Auto-indentation

  • Auto closing of brackets / quotes

  • Undo / redo

  • Find & replace

  • Re-size text editor

• Integrations and Notifications. The Console area covering these key functions have undergone significant consolidation and rework to give a better overall user experience in terms of core workflows for creating and configuring, and for ease of management:

  • Integrations. The main page shows a grid layout for the external systems available for integration and can be filtered for either Accounts Receivable or CRM systems. Each external system now has its own page for configuring and managing Native Integrations with the system, and incorporates a Credentials section.

  • Notifications. Similarly, once a Notification Webhook Integration has been set up, management is done from a single page for the Notification rule details, including linking to Outgoing Webhooks and reviewing Events for the Notification.

• Segmented Aggregations. When setting up a segmented Aggregation, the Segments panel now extends the full width of the page to accommodate longer text entries for segment values.

• Accounting Product IDs. These are now clearly shown on the details pages in the Console for relevant billing-related entities and for linking to Bill line items: Prepayment/Commitments for fees and usage; Plans for minimum spends and standing charges; Pricings for usage and minimum spends; Counter Pricings for recurring charges; Balances for consumption draw-downs.

Balance Transactions. When creating Transactions for Balances in the Console, users can now define a Transaction date and an Applied date, and these are now clearly shown on the Balance Transactions ledger. There is no restriction on back-dating Transactions, which is useful for certain use cases such as when contract renewal negotiations for an end-customer Account are protracted.

Resolved Issues

• Fix: The to-date options for date range setting for operational data exports now set the range to end at the minute a selection is made, and instead of setting the date range to end at the start of the following day.

• Fix: An issue where dimension fields on Usage Explorer V1 did not reset correctly has been resolved.

• Fix: If productId was missing for line items, then duplicate line items could appear on Bills. This has now been resolved.

• Fix: When a Prepayment/Commitment on an Account is configured to be billed on a schedule, an issue where the service period end date appeared on Bills as the day prior has been resolved.

Version: February 2025

Product Updates

Accounting Products for Billing Elements. The range and granularity of billing elements in m3ter that can be assigned an accounting product has been extended to include:

• Prepayments/Commitments:

  • Fees

  • Usage draw-downs

• Pricings and Counter Pricings. Allows pricing metric accounting (Aggregation and Counter-level).

• Plans:

  • Standing Charges

  • Minimum Spends

• Balances:

  • Fees

  • Consumption draw-downs

By allowing assignment of accounting products at these various levels, m3ter ensures that each bill line item can be correctly categorized for accounting purposes

Data Exports Service:

• Ad-hoc Operational Exports. Some additional options are now available when running these data exports:

  • Define a date/time range to include only the data created or modified within that time period.

  • Include Balance Transactions data in the export.

• Downloads to Local Device. Available through the API - if a Destination is omitted, a Data Export file download URL can be obtained for the export job and then used to download the file to your local device.

Recurring Charges. You can now enter a value of 0 for a Counter Adjustment on an Account, which is useful if an end-customer wants to terminate a contract mid-billing period.

Integrations:

• External Mappings. When setting up External Mappings for integrations, custom External Table names can now be used for the mapping. This is especially useful when integrating with systems that support custom objects, such as Salesforce.

• Bill Integration Runs. From the Bill details card you can now open and review all integration runs for a Bill. This serves several common use cases: where a single Bill is subject to multiple integration runs, Bills are synced to multiple external Accounts Receivable (AR) systems, or Bills are synced to multiple instances of the same external AR system.

• Balances. The Balance details card in the Console now provides a comprehensive set of fields that allow users to closely review and track key Balance amounts, including any rollover amount originally defined for the Balance and the remaining rollover amount.

Console Updates

Usability Improvements:

• Table Style. A new style has been implemented for tables across Console pages, which provides bolded text header rows and sharper contrast for content rows when viewing.

• Search Accounts. Users can now use the Account ID to search the Accounts list page.

Resolved Issues

• Fix: When attaching Plans to an Account, the start date and end date selectors on the Create Plan attachment page now allow users to select a time as well as a date.

• Fix: If the Organization timezone was set at other than UTC, an issue is now resolved which allowed the start and end dates of a Prepayment/Commitment or Contract to be set incorrectly.

• Fix: If the Meters list has been filtered by Product, the Product selection is now retained for starting the create Meter workflow, and relieves the user from having to re-select the Product to start the workflow.

• Fix: When a Single Sign-On (SSO) failure occurs, users are now shown an error message for the failure in the Console.

• Fix: If a unit is not defined for a Bill line item type, then the unit is now shown as having no value where previously a zero value was shown, which could be misleading.

Version: January 2025

Product Updates

• Data Export Service. A Data Export service is now available in m3ter in Preview release version. You can use this new service to export usage data and operational data from your m3ter Organization directly into your AWS S3 buckets. Configure data export schedules to run at hourly or daily intervals or run ad-hoc data exports:

  • Usage Data. Specify a precise range of usage data measurements ingested for your Organization that you want to export - by Meter, Account, and time period. You can select to aggregate the specified usage data for exporting, if required.

  • Operational Data. Export the configuration and operational data for a range entities from your production environment - such as Bills, Prepayments/Commitments, Accounts, and Balances.

  • See Data Exports (Preview) for more details.

• Salesforce Native Integrations. When setting up Salesforce native integrations for either billing or entity data, you can now select a Namespace to specify where in your Salesforce Org you want to sync data to. See External System Configuration for more details.

Console Updates

• Outgoing Webhooks for Notifications. When configuring integrations for Notifications based on system or scheduled events, the webhooks you create for where a Notification's payload will be delivered are now called Outgoing Webhooks. This makes the configuration workflow for implementing Notifications in m3ter simpler and more intuitive. See Creating and Managing Outgoing Webhooks for more details.

• Usability Improvements:

  • Segmented Aggregations. When users select the target Meter fields they want to segment aggregated usage by, a default row is now added automatically allowing them to promptly add required segments.

  • Date/Time Selection Fields. For start and end dates that include a time component, Date/Time selectors in the Console now offer time selections to 15 minutes of granularity, and the selected Date/Time is clearly displayed in the form fields.

Resolved Issues

• Fix: When deploying Counter pricing for recurring charges against end-customer Accounts, Counter values can now be set at zero to accommodate cases where an end-customer terminates their contract in the middle of the billing cycle.

• Fix: An issue has been resolved for an error showing when attempting to enter decimal place amounts for setting up Prepayment billing on a schedule.

• Fix: Rows on UI forms when one has a Help text associated now align correctly.

Additional Support