Update OrganizationConfig

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.

Sets the timezone for the Organization.

Optional setting that defines the billing cycle date for Accounts that are billed yearly. Defines the date of the first Bill and then acts as reference for when subsequent Bills are created for the Account:

• For example, suppose the Plan you attach to an Account is configured for yearly billing frequency and will apply to the Account from January 1st, 2022 until January 15th, 2028. If you set a yearEpoch date of January 1st, 2023, then the first Bill is created for the Account on that date and subsequent Bills are created for the Account on January 1st of each year following through to the end of the billing service period - January 1st, 2023, January 1st, 2024 and so on.
• The date is in ISO-8601 format.

Optional setting that defines the billing cycle date for Accounts that are billed monthly. Defines the date of the first Bill and then acts as reference for when subsequent Bills are created for the Account:

• For example, suppose the Plan you attach to an Account is configured for monthly billing frequency and will apply to the Account from January 1st, 2022 until June 30th, 2022. If you set a monthEpoch date of January 15th, 2022, then the first Bill is created for the Account on that date and subsequent Bills are created for the Account on the 15th of each month following through to the end of the billing service period - February 15th, March 15th, and so on.
• The date is in ISO-8601 format.

Optional setting that defines the billing cycle date for Accounts that are billed weekly. Defines the date of the first Bill and then acts as reference for when subsequent Bills are created for the Account:

• For example, suppose the Plan you attach to an Account is configured for weekly billing frequency and will apply to the Account from January 1st, 2022 until June 30th, 2022. If you set a weekEpoch date of January 15th, 2022, which falls on a Saturday, then the first Bill is created for the Account on that date and subsequent Bills are created for the Account on Saturday of each week following through to the end of the billing service period.
• The date is in ISO-8601 format.

Optional setting that defines the billing cycle date for Accounts that are billed daily. Defines the date of the first Bill:

• For example, suppose the Plan you attach to an Account is configured for daily billing frequency and will apply to the Account from January 1st, 2022 until June 30th, 2022. If you set a dayEpoch date of January 2nd, 2022, then the first Bill is created for the Account on that date and subsequent Bills are created for the Account each day following through to the end of the billing service period.
• The date is in ISO-8601 format.

The currency code for the Organization. For example: USD, GBP, or EUR:

• This defines the billing currency for the Organization. You can override this by selecting a different billing currency at individual Account level.
• You must first define the currencies you want to use in your Organization. See the Currency section in this API Reference.

Note: If you use a different currency as the pricing currency for Plans to set charge rates for Product consumption by an Account, you must define a currency conversion rate from the pricing currency to the billing currency before you run billing for the Account, otherwise billing will fail. See below for the currencyConversions request parameter.

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.

Sets the required interval for updating bills. It is an optional parameter that can be set as:

• For portions of an hour (minutes). Two options: 0.25 (15 minutes) and 0.5 (30 minutes).
• For full hours. Enter 1 for every hour, 2 for every two hours, and so on. Eight options: 1, 2, 3, 4, 6, 8, 12, or 24.
• Default. The default is 0, which disables scheduling.

Boolean setting to specify whether the standing charge is billed in advance at the start of each billing period, or billed in arrears at the end of each billing period.

• TRUE - bill in advance (start of each billing period).
• FALSE - bill in arrears (end of each billing period).

Boolean setting to specify whether commitments (prepayments) are billed in advance at the start of each billing period, or billed in arrears at the end of each billing period.

• TRUE - bill in advance (start of each billing period).
• FALSE - bill in arrears (end of each billing period).

Boolean setting to specify whether minimum spend amounts are billed in advance at the start of each billing period, or billed in arrears at the end of each billing period.

• TRUE - bill in advance (start of each billing period).
• FALSE - bill in arrears (end of each billing period).

Grace period before bills are auto-approved. Used in combination with autoApproveBillsGracePeriodUnit parameter.

Note: When used in combination with autoApproveBillsGracePeriodUnit enables auto-approval of Bills for Organization, which occurs when the specified time period has elapsed after Bill generation.

Time unit of grace period before bills are auto-approved. Used in combination with autoApproveBillsGracePeriod parameter. Allowed options are MINUTES, HOURS, or DAYS.

Note: When used in combination with autoApproveBillsGracePeriod enables auto-approval of Bills for Organization, which occurs when the specified time period has elapsed after Bill generation.

Date to use for the invoice date. Allowed values are FIRST_DAY_OF_NEXT_PERIOD or LAST_DAY_OF_ARREARS.

Boolean setting that supresses generating bills that have no line items.

• TRUE - prevents generating bills with no line items.
• FALSE - bills are still generated even when they have no line items.

Boolean setting to consolidate different billing frequencies onto the same bill.

• TRUE - consolidate different billing frequencies onto the same bill.
• FALSE - bills are not consolidated.

Organization level default statementDefinitionId to be used when there is no statement definition linked to the account.

Statement definitions are used to generate bill statements, which are informative backing sheets to invoices.

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.

Allow balance amounts to fall below zero. This feature is enabled on request. Please get in touch with m3ter Support or your m3ter contact if you would like it enabling for your organization(s).

Allows plans to overlap time periods for different contracts.

Prefix to be used for sequential invoice numbers. This will be combined with the sequenceStartNumber.

NOTES:

• If you do not define a billPrefix, a default will be used in the Console for the Bill REFERENCE number. This default will concatenate INV- with the last four characters of the billId.
• If you do not define a billPrefix, the Bill response schema for API calls that retrieve Bill data will not contain a sequentialInvoiceNumber.

The starting number to be used for sequential invoice numbers. This will be combined with the billPrefix.

For example, if you define billPrefix to be INVOICE- and you set the seqenceStartNumber as 100, the first Bill created after updating your Organization Configuration will have a sequentialInvoiceNumber assigned of INVOICE-101. Subsequent Bills created will be numbered in time sequence for their initial creation date/time.

The UUID of the entity.

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.

The timezone for the Organization.

The first bill date (in ISO-8601 format) for yearly billing periods.

The first bill date (in ISO-8601 format) for monthly billing periods.

The first bill date (in ISO-8601 format) for weekly billing periods.

The first bill date (in ISO-8601 format) for daily billing periods.

The currency code for the currency used in this Organization. For example: USD, GBP, or EUR.

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

Specifies the required interval for updating bills.

• For portions of an hour (minutes). Two options: 0.25 (15 minutes) and 0.5 (30 minutes).
• For full hours. Eight possible values: 1, 2, 3, 4, 6, 8, 12, or 24.
• Default. The default is 0, which disables scheduling.

Specifies whether the standing charge is billed in advance at the start of each billing period, or billed in arrears at the end of each billing period.

• TRUE - bill in advance (start of each billing period).
• FALSE - bill in arrears (end of each billing period).

Specifies whether commitments (prepayments) are billed in advance at the start of each billing period, or billed in arrears at the end of each billing period.

• TRUE - bill in advance (start of each billing period).
• FALSE - bill in arrears (end of each billing period).

Specifies whether minimum spend amounts are billed in advance at the start of each billing period, or billed in arrears at the end of each billing period.

• TRUE - bill in advance (start of each billing period).
• FALSE - bill in arrears (end of each billing period).

Grace period before bills are auto-approved. Used in combination with the field autoApproveBillsGracePeriodUnit.

Time unit of grace period before bills are auto-approved. Used in combination with the field autoApproveBillsGracePeriod.

The date to use for the invoice date.

Specifies whether to supress generating bills that have no line items.

• TRUE - prevents generating bills with no line items.
• FALSE - bills are still generated even when they have no line items.

Specifies whether to consolidate different billing frequencies onto the same bill.

• TRUE - consolidate different billing frequencies onto the same bill.
• FALSE - bills are not consolidated.

Organization level default statementDefinitionId to be used when there is no statement definition linked to the account.

Statement definitions are used to generate bill statements, which are informative backing sheets to invoices.

Prefix to be used for sequential invoice numbers. This will be combined with the sequenceStartNumber.

The starting number to be used for sequential invoice numbers. This will be combined with the billPrefix.

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.

Allow balance amounts to fall below zero. This feature is enabled on request. Please get in touch with m3ter Support or your m3ter contact if you would like it enabling for your organization(s).

Allows plans to overlap time periods for different contracts.

The DateTime when the organization config was created (in ISO-8601 format).

The DateTime when the organization config was last modified (in ISO-8601 format).

The id of the user who created this organization config.

The id of the user who last modified this organization config.