• Home
/
• Working in m3ter - User Guides
/
• Integrations

m3ter Integrations - Overview

By exploiting the m3ter open-API framework, you can use m3ter Integrations to quickly map and synchronize data held in any 3rd-party systems you use for core business operations, such as sales, pricing, billing and invoicing, and general finance.

m3ter Integrations enable you to quickly set up and implement highly configurable usage-based pricing models for your new or existing external system or service. You can then charge your customers based on what they use, instead of charging by subscription under a one-price-fits-all pricing model. Integrations are seamless, which means you only need to ingest consumption usage data into m3ter in order to be able to bill via your regular account receivable invoicing system.

You can also then leverage this data synchronization between m3ter and your other systems to implement a wide range of use cases to serve wider business operational requirements.

A typical Integration combines three data flows into a seamless and unified data exchange and synchronization pipeline for end customer sales/subscriptions/usage through to usage-based billing and invoicing in your 3rd-party system:

1. Subscription/Order/Sales flow into m3ter. End customer account and subscription/order/sales details from 3rd-party system into m3ter.

2. Usage Data Ingest for Metering. End customer product usage data and events ingested into m3ter to drive usage-based pricing.

3. Billing Flow. From m3ter Bills out to 3rd-party invoicing and payments.

This topic describes at high-level some common m3ter integrations with 3rd-party systems and services:

• Paddle

• Chargebee

• Stripe

• NetSuite

• Xero

• Quickbooks

Paddle

1. Checkout and Subscribe Flow: Paddle to m3ter. Upon successful Checkout completion in Paddle by an end Customer, a Subscription Created webhook is triggered and captured by m3ter via the connector. An Account and Account Plan are created in m3ter, which contain the mapped Paddle Subscription Plan.

2. Usage Data Ingest for Metering. End customer usage data measures and events are submitted and ingested into m3ter via API calls or file uploads. See Submitting Usage Data and our Submit measurements API Reference documentation.

3. Billing Flow: m3ter to Paddle. m3ter Bills can be generated as often as required during the billing period. When a Bill is approved, the integration creates billing modifiers in Paddle via the connector.

Chargebee

1. Subscription Flow: Chargebee into m3ter. When a Subscriber and their Subscription are created in Chargebee, a webhook is triggered and captured by m3ter. This causes an Account and Account Plan to be created respectively in m3ter. If subsequently a Subscription is cancelled in Chargebee, a webhook is triggered and the end date supplied by Chargebee is set on the corresponding Account Plan in m3ter.

2. Usage Data Ingest for Metering. End customer usage data measures and events are submitted and ingested into m3ter via API calls or file uploads. See Submitting Usage Data and our Submit measurements API Reference documentation.

3. Billing Flow: m3ter into Chargebee. Bills in m3ter can be generated several times. When the Bill is ready to be sent to Chargebee for invoicing, the bill must be approved. On Bill approval in m3ter, the webhooks connector is triggered and Charge Items are created against the Chargebee Pending invoice.

Stripe

1. Checkout and Subscribe Flow: Stripe to m3ter. Upon successful Checkout completion in Stripe by an end Customer, a Subscription Created webhook is triggered and captured by m3ter via the connector. An Account and Account Plan are created in m3ter, which are linked to Stripe Customer and Stripe Subscription Plan respectively.

2. Usage Data Ingest for Metering. End customer usage data measures and events are submitted and ingested into m3ter via API calls or file uploads. See Submitting Usage Data and our Submit measurements API Reference documentation.

3. Billing Flow: m3ter to Stripe. m3ter Bills can be generated as often as required during the billing period. There are two options for when billing data is sent through from m3ter to Stripe:

• Every time a Bill is generated.

• Only when a generated Bill is approved.

This is configurable and, depending on the option you configure, invoice items are created as a result of the appropriate event in Stripe via the connector.

There are also additional configurable options for your Stripe integration, depending on the way you have configured your Stripe system:

• Stripe Invoicing. A Stripe Invoice is created with Debit Items loaded if this is the first Billing run. On subsequent Billing, the Stripe Invoice Debit Items are updated.

• Stripe Subscription Invoicing. A Stripe Invoice is not created. Invoice Debit Items are created and these are associated with the Stripe Customer - Stripe will then automatically add these Debit Items to an Invoice when raised.

NetSuite

1. Sales Flow: 3rd-Party Systems into m3ter. When a Customer and their Order/Quote are created in a 3rd-party sales channel, a webhook is triggered and captured by m3ter. This causes an Account and Account Plan to be created respectively in m3ter.

2. Usage Data Ingest for Metering. End customer usage data measures and events are submitted and ingested into m3ter via API calls or file uploads. See Submitting Usage Data and our Submit measurements API Reference documentation.

3. Billing Flow: m3ter into NetSuite. Bills in m3ter can be generated several times. A Bill can be sent to NetSuite without being approved. So, Bills can be updated throughout the month with the latest information then approved at the end.

Xero

1. Sales Flow: 3rd-Party Systems into m3ter. When a Customer and their Order/Quote are created in a 3rd-party sales channel, a webhook is triggered and captured by m3ter. This causes an Account and Account Plan to be created respectively in m3ter.

2. Usage Data Ingest for Metering. End customer usage data measures and events are submitted and ingested into m3ter via API calls or file uploads. See Submitting Usage Data and our Submit measurements API Reference documentation.

3. Billing Flow: m3ter into Xero. Bills in m3ter can be generated several times. When the Bill is ready to be sent to Xero for invoicing, the Bill must be approved. On Bill approval in m3ter, the webhooks connector is triggered and Bill line items are sent through as Xero Invoice and Invoice items.

QuickBooks

1. Sales Flow: 3rd-Party Systems into m3ter. When a Customer and their Order/Quote are created in a 3rd-party sales channel, a webhook is triggered and captured by m3ter. This causes an Account and Account Plan to be created respectively in m3ter.

2. Usage Data Ingest for Metering. End customer usage data measures and events are submitted and ingested into m3ter via API calls or file uploads. See Submitting Usage Data and our Submit measurements API Reference documentation.

3. Billing Flow: m3ter into QuickBooks. Bills in m3ter can be generated several times. When the Bill is ready to be sent to QuickBooks for invoicing, the Bill must be approved. On Bill approval in m3ter, the webhooks connector is triggered and Bill line items are sent through as QuickBooks Invoice and Invoice items.

Next: Setting Up and Managing Native and Notification Integrations

Additional Support