In the legacy OrderMetrics, users could configure general costs manually as “Custom Spends”. With the launch of the all-new OrderMetrics, we have reimagined and renamed this feature to “Operating Costs”.

All of your custom spends from the legacy OrderMetrics will be migrated to the all-new OrderMetrics. Since the all-new OrderMetrics has a pre-built set of categories, we will map your custom spends from the legacy OrderMetrics to these categories automatically:

  • Advertising & Marketing

  • Banking Fees

  • Consulting & Contractors

  • Interest Expense

  • Meals & Entertainment

  • Office & General Expenses

  • Professional Services Fees

  • Rent

  • Salaries & Wages

  • Software & Subscriptions

  • Transaction Fees

  • Travel Expenses

  • Utilities

If any of your custom spends do not fit into any of the categories above, they will be automatically mapped to the “Office & General Expenses” category.

Note: In the all-new OrderMetrics, newly created operating costs are automatically split across each day of the month. For example, if you create an operating cost of $1,000 on Jan 17, we will split this $1,000 across each of the 31 days in January. So your operating cost for Jan 17 will be $32.25, not $1,000.

Also, new operating costs you create will be adjusted in your metrics at the next daily sync. For example, if you create an operating cost at 5 pm local time, it will be factored into your metrics at 12:00 am local time next day (when the next daily sync occurs).

What about recurring Custom Spends?

These are now known as Scheduled Costs.

  • We map all schedules to Monthly

  • For Yearly expenses, we divide the amount by 12 (since it is becoming monthly)

  • For weekly expenses, we multiply by 4

  • The next date for the Scheduled Expense is the next date in the series (for most, this will be the first of the following month, except where the schedule was Yearly, in which case it may be 5/1/21 for example).

  • We materialize the historical schedule into costs based on the configured series in the legacy OrderMetrics

Did this answer your question?