Managing Accounts - Best Practices

This topic offers some notes on best practices for managing the Accounts in your Organization. These notes are intended to help you avoid any unintended and unwanted issues with your end-customer Accounts:

Personally Identifiable Information (PII)

Under the Data Processing Agreement, the only fields you are allowed to use for any of your end customer PII data in m3ter are the name, address, and emailAddress fields on the Account entity.

For more details see:

The request schema for the Create Account API call as documented in our API Reference.
The following Creating and Editing Accounts topic.
Section 4.2 of the Terms of Service.

Best Practice:

Please comply with these constraints on the use of Personally Identifiable Information (PII) when creating end-customer Accounts for your m3ter Organization.

Editing and Deleting Accounts - Implications for Usage Data

The Usage Data measurements ingested for Accounts are key to the usage-based pricing applied to Product Plans used to charge and Bill Accounts that consume your Products. It's important to understand clearly how that usage data is associated with Accounts and what the implications are when it comes to editing or deleting Accounts.

How are the usage data ingested for an Account linked to the Account?

When usage data measurements are ingested into the platform, you submit them using the relevant Meter and Account Codes. However, once ingested, and for subsequent configuration and data management purposes, the usage data is linked strictly to the Account and Meter ids.

Note: Auto-created Accounts? For usage data submission you make when the Account does not yet exist for your Organization, the system will auto-create an Account for you. But the result is the same as when the Account does already exist - the usage data is linked strictly to the new Account's id.

When is the Account id created and how do I find out what it is?

To create an Account, you supply the Code you want to use for the Account. On successful creation, the system generates a unique id and assigns it to the new Account:

If you open an Account's Details page in the Console, the Account id is listed and you can copy it directly to your clipboard.
Alternatively, you can submit a List Accounts API call and use a codes query parameter for a specific Account. The response schema will contain the Account id.

What are the consequences if I delete an Account after submitting usage data for the Account?

If you delete the Account, any submitted usage data linked to the Account's id are permanently dissociated from it.

If I have no option but to delete and recreate an Account, what are the consequences?

In this sort of case, the key issue to consider is whether or not you have already submitted usage data for the Account:

If you have not, then you can delete the Account and recreate it and begin submitting usage data, which will then be linked to the Account id in the normal way.
If you have, you cannot use that previously ingested usage data for billing against the recreated Account. You will have to re-submit the usage data to the recreated Account for the data to become available for billing against the Account.

Note: Recreated Account uses same Code? This is the case even if you use the same Code for the recreated Account as the Code that was used for the original and now deleted Account.

Best Practice:

In view of these considerations, we strongly recommend that wherever possible you avoid deleting Accounts and instead update Accounts. You can edit and update an Account, including the Code, and continue to submit and ingest usage data seamlessly for the Account with the data continuously linked to the Account's unique id.

Next: Creating, Editing, and Deleting Accounts