Use this index listing to quickly find information about specific m3ter entities or areas of functionality.
Represents one of your end-customer accounts:
Plans are attached to Accounts to create Account Plans, which then determine the charges incurred by your end customer.
Plan Groups are attached to Accounts to create Account Plan Groups, which then determine the charges incurred by your end customer.
Aggregations define how to convert into a single number individual usage data measurements collected by Meter fields. They are used to configure pricing for Product Plans.
Balances are created for end customer Accounts. A credit Balance amount can then be draw-down against for any charges due throughout the period the Balance is active for the Account. Transactions can be added manually to top-up the original Balance and a Transactions ledger is maintained for the Balance:
Bills are generated for an Account based on the usage-based pricing Plan that has been attached to the Account for charging the Account for consuming a Product. Plan Templates/Plans offer settings to control billing on Accounts that Product Plans are attached to for charging the Accounts.
A Child Account is an Account that has a Parent Account defined. End customers with multiple Accounts can be issued with a single Bill for a Parent Account.
A Compound Aggregation allows you to define an Aggregation that is based on other (simple) Aggregations using a calculation.
Contracts are created for Accounts. For end customers who consume several different service or product packages, the total Contract value can be reported for accounting purposes.
The currency used for billing is set at the level of your Organization or at the level of an individual Account. You can also define a different currency for your Plans at the Plan Template level. If you do this, the Organization or Account setting is used for billing and you can configure currency conversion rates to determine how charge amounts in the Plan currency are converted into Organization currency amounts.
Custom Fields allow you to attach custom data to your Organization and some other individual m3ter entities.
Data Explorer allows you to query data collected for your Organization in the m3ter service for Usage, Billing, and Prepayments/Commitments.
Data Fields are added to Meters and define a raw usage data collection fields.
Derived Fields are configured for Meters and use calculations on other fields to define usage data collection fields. Calculations can reference Meter Data Fields, Custom Fields, and system timestamp fields.
You can use Events generated in m3ter as the basis for setting up and sending Notifications into your external systems when those Events occur and the specific conditions you've defined for triggering a Notification are satisifed:
External Mappings are mapping reference lookups, which store unique ids for matched objects across two or more systems.
Global Meters do not belong to a specific Product, and are used to set up usage-based pricing across different Products.
Integrations exploit m3ter's open-API framework allowing you to quickly map and synchronize data held in any 3rd-party systems you use for core business operations.
Meters define the Data Fields that your system will submit to the m3ter service as usage data. They can be created as Product-specific Meters or as Global Meters.
You can set up Notifications to be triggered and sent into external systems on the basis of m3ter-generated Events. This includes the capability to create rule sets to define the precise conditions under which a Notification will be triggered and sent out when a specific Event occurs:
An Organization represents your company as a direct customer of the m3ter service.
Permission Policies allow you to control what users who have authenticated with the service are allowed to do in your Organization.
Plans represent a pricing and billing plan for end customers who consume your products or services. They are derived from Plan Templates.
Plan Groups allow you to group together Plans for different Products and define a minimum spend for the Group.
Plan Templates allow you to configure default billing and pricing settings for your Plans, avoiding repetition in configuration work when setting up Plans.
Prepayments/Commitments allow you to assign an amount to an Account that the end customer has agreed to pay over the duration of their contract with you.
Pricing allows you to use Aggregations to configure the cost of usage data consumed under a Plan.
Products represent the products or service that your Organization offers to end customers.
Segmented Aggregations allow you to segment the usage data collected by a single Meter and price your Plans by these segment values.
Service Users represent automated processes that you want to grant direct API access to your Organization.
Users represent a person you allow to authenticate with and have access to your Organization.