Sign in
Account

Update Account

Update the Account with the given Account UUID.

Note: If you have created Custom Fields for an Account, when you use this endpoint to update the Account, use the customFields parameter to preserve those Custom Fields. If you omit them from the update request, they will be lost.

put/organizations/{orgId}/accounts/{id}

Path parameters

orgIdstring required

UUID of the Organization. The Organization represents your company as a direct customer of the m3ter service.

idstring required

The UUID of the Account to update.

Request body

versioninteger

The version number of the entity:

  • Create entity: Not valid for initial insertion of new entity - do not use for Create. On initial Create, version is set at 1 and listed in the response.
  • Update Entity: On Update, version is required and must match the existing version because a check is performed to ensure sequential versioning is preserved. Version is incremented by 1 and listed in the response.
customFieldsobject

User defined fields enabling you to attach custom data. The value for a custom field can be either a string or a number.

If customFields can also be defined for this entity at the Organizational level, customField values defined at individual level override values of customFields with the same name defined at Organization level.

See Working with Custom Fields in the m3ter documentation for more information.

namestring required

Name of the Account.

codestring required

Code of the Account. This is a unique short code used for the Account.

emailAddressstring email required

Contact email for the Account.

configDataobject

Configuration data for the Account Supported settings:

  • SendBillsToThirdParties ("true"/"false")
parentAccountIdstring

Parent Account ID, or null if this Account does not have a parent.

billEpochstring date

Optional setting to define a billing cycle date, which sets the date of the first Bill and acts as a reference for when in the applied billing frequency period subsequent bills are created:

  • For example, if you attach a Plan to an Account where the Plan is configured for monthly billing frequency and you've defined the period the Plan will apply to the Account to be from January 1st, 2022 until January 1st, 2023. You then set a billEpoch date of February 15th, 2022. The first Bill will be created for the Account on February 15th, and subsequent Bills created on the 15th of the months following for the remainder of the billing period - March 15th, April 15th, and so on.
  • If not defined, then the relevant Epoch date set for the billing frequency period at Organization level will be used instead.
  • The date is in ISO-8601 format.
purchaseOrderNumberstring

Purchase Order Number of the Account.

Optional attribute - allows you to set a purchase order number that comes through into invoicing. For example, your financial systems might require this as a reference for clearing payments.

currencystring

Account level billing currency, such as USD or GBP. Optional attribute:

  • If you define an Account currency, this will be used for bills.
  • If you do not define a currency, the billing currency defined at Organizational level will be used.

Note: If you've attached a Plan to the Account that uses a different currency to the billing currency, then you must add the relevant currency conversion rate at Organization level to ensure the billing process can convert line items calculated using the Plan currency into the selected billing currency. If you don't add these conversion rates, then bills will fail for the Account.

statementDefinitionIdstring

The UUID of the statement definition used when Bill statements are generated for the Account. If no statement definition is specified for the Account, the statement definition specified at Organizational level is used.

Bill statements can be used as informative backing sheets to invoices. Based on the usage breakdown defined in the statement definition, generated statements give a breakdown of usage charges on Account Bills, which helps customers better understand usage charges incurred over the billing period.

See Working with Bill Statements in the m3ter documentation for more details.

autoGenerateStatementMode'NONE' | 'JSON' | 'JSON_AND_CSV'

Specify whether to auto-generate statements once Bills are approved or locked. It will not auto-generate if a bill is in pending state.

The default value is None.

  • None. Statements will not be auto-generated.
  • JSON. Statements are auto-generated in JSON format.
  • JSON and CSV. Statements are auto-generated in both JSON and CSV formats.
creditApplicationOrderBillCreditType[]

Define the order in which any Prepayment or Balance amounts on the Account are to be drawn-down against for billing. Four options:

  • "PREPAYMENT","BALANCE". Draw-down against Prepayment credit before Balance credit.
  • "BALANCE","PREPAYMENT". Draw-down against Balance credit before Prepayment credit.
  • "PREPAYMENT". Only draw-down against Prepayment credit.
  • "BALANCE". Only draw-down against Balance credit.

NOTES:

  • Any setting you define here overrides the setting for credit application order at Organization level.
  • If the Account belongs to a Parent/Child Account hierarchy, then the creditApplicationOrder settings are not available, and the draw-down order defaults always to Prepayment then Balance order.
daysBeforeBillDueinteger

Enter the number of days after the Bill generation date that you want to show on Bills as the due date.

Note: If you define daysBeforeBillDue at individual Account level, this will take precedence over any daysBeforeBillDue setting defined at Organization level.

Example request

{
  "currency": "USD"
}

Response

Returns the updated Account

idstring required

The UUID of the entity.

versioninteger

The version number:

  • Create: On initial Create to insert a new entity, the version is set at 1 in the response.
  • Update: On successful Update, the version is incremented by 1 in the response.
customFieldsobject

User defined fields enabling you to attach custom data. The value for a custom field can be either a string or a number.

If customFields can also be defined for this entity at the Organizational level,customField values defined at individual level override values of customFields with the same name defined at Organization level.

See Working with Custom Fields in the m3ter documentation for more information.

namestring

Name of the Account.

codestring

Code of the Account. This is a unique short code used for the Account.

emailAddressstring

Contact email for the Account.

configDataobject

Configuration data for the Account

parentAccountIdstring

Parent Account ID, or null if this account does not have a parent.

billEpochstring date

Defines first bill date for Account Bills. For example, if the Plan attached to the Account is set for monthly billing frequency and you set the first bill date to be January 1st, Bills are created every month starting on that date.

Optional attribute - if not defined, then first bill date is determined by the Epoch settings at Organizational level.

purchaseOrderNumberstring

Purchase Order Number of the Account.

Optional attribute - allows you to set a purchase order number that comes through into invoicing. For example, your financial systems might require this as a reference for clearing payments.

currencystring

Account level billing currency, such as USD or GBP. Optional attribute:

  • If you define an Account currency, this will be used for bills.
  • If you do not define a currency, the billing currency defined at Organizational will be used.

Note: If you've attached a Plan to the Account that uses a different currency to the billing currency, then you must add the relevant currency conversion rate at Organization level to ensure the billing process can convert line items calculated using the Plan currency into the selected billing currency. If you don't add these conversion rates, then bills will fail for the Account.

statementDefinitionIdstring

The UUID of the statement definition used when Bill statements are generated for the Account. If no statement definition is specified for the Account, the statement definition specified at Organizational level is used.

Bill statements can be used as informative backing sheets to invoices. Based on the usage breakdown defined in the statement definition, generated statements give a breakdown of usage charges on Account Bills, which helps customers better understand usage charges incurred over the billing period.

See Working with Bill Statements in the m3ter documentation for more details.

dtCreatedstring date-time

The DateTime when the Account was created (in ISO 8601 format).

dtLastModifiedstring date-time

The DateTime when the Account was last modified (in ISO 8601 format).

createdBystring

The ID of the user who created the account.

lastModifiedBystring

The ID of the user who last modified the Account.

autoGenerateStatementMode'NONE' | 'JSON' | 'JSON_AND_CSV'

Specify whether to auto-generate statements once Bills are approved or locked. It will not auto-generate if a bill is in pending state.

The default value is None.

  • None. Statements will not be auto-generated.
  • JSON. Statements are auto-generated in JSON format.
  • JSON and CSV. Statements are auto-generated in both JSON and CSV formats.
creditApplicationOrderBillCreditType[]

The order in which any Prepayment or Balance amounts on the Account are to be drawn-down against for billing. Four options:

  • "PREPAYMENT","BALANCE". Draw-down against Prepayment credit before Balance credit.
  • "BALANCE","PREPAYMENT". Draw-down against Balance credit before Prepayment credit.
  • "PREPAYMENT". Only draw-down against Prepayment credit.
  • "BALANCE". Only draw-down against Balance credit.
daysBeforeBillDueinteger

The number of days after the Bill generation date shown on Bills as the due date.

Example response

{
  "currency": "USD"
}

Changes

Changed in 2 of the 10 revisions of this API.31

  • 9f9e5f3dbde72See the full diff
    • ▲

      the response property allOf[AbstractResponseWithCustomFields]/allOf[AbstractResponse]/version became optional for the status 200

      response-property-became-optional

    • ▲

      the response property allOf[AbstractResponse]/version became optional for the status 200

      response-property-became-optional

    This revision also has 53 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • d064a12d0d9311See the full diff
    • ▲

      the allOf[AbstractRequestWithCustomFields]/allOf[subschema #2]/customFields request property type/format changed from / to object/

      request-property-type-changed

    • ●

      removed subschema #1 subschema #2 from the allOf[AbstractRequestWithCustomFields]/allOf[subschema #2]/customFields request property allOf list

      request-property-all-of-removed

    This revision also has 6 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog