Metronome can be the heart of your entire billing system, combining multiple integrations, from CRM to invoicing to reporting. These third-party systems may have their own additional integrations, such as automated tax calculations.
Entity mapping allows you to configure your integrations so they work better together. For example, you can pass additional data on your Stripe invoices to trigger Stripe's TaxJar functionality.
Entity mapping is supported for Stripe and NetSuite integrations.
How entity mapping works
Entity mapping uses custom fields to identify additional data to be sent to an integration. Each integration expects specifically named data:
- Anrok: pass a Stripe product ID to
- Avalara: pass a
- TaxJar: pass a
product_tax_codeto Products or Charges
1. Define and populate the custom fields
For example, to configure the Stripe TaxJar integration, a product price needs to be passed to Stripe's
invoiceitem.price field. Create a custom field on Product named
2. Populate the custom fields
After creating the necessary custom fields on your Metronome entities, add the appropriate values for your instances. For example, assign the correct price to an individual Product's
3. Map entities in the Metronome app
Next use the Metronome app to configure the entity mapping for the integration. To continue with the Stripe TaxJar example:
- Click General settings.
- On the resulting page, click the Edit mapping for the Stripe integration.
- In the resulting model, select
invoiceitem.pricefor the Stripe Entity
productfor Stripe Key
Productfor the Metronome Entity
stripe_taxjar_invoiceitem_pricefor the Metronome Key
- Click Save.
With the entities mapped, the next time you process an invoice with Stripe, the custom field data is passed along. When Stripe receives that field, the TaxJar integration is triggered, dynamically adding correct tax calculations to your invoice.