1. Monthly
2. Quarterly
3. Others

Thanks for your time

2-3 times per month.

Monthly

We load our cost transparency project data once a month and our cloud project data daily.  I am considering loading CT more than once a month, but haven't pulled that trigger yet.

Monthly

Monthly

Thank you all. This is helpful. We are currently doing monthly. We are thinking if we should change it, hence the poll :-)

Monthly !

We load actuals monthly, forecasts quarterly.

We load partial actuals on the 1st business day of the month for forecast in IT Planning and then a full actuals file following close.

Monthly for most data, some is quarterly.

Weekly for our GL data, monthly for our people data.

Monthly.

We load them monthly.

Monthly. What are the main reasons to do it more frequently? 

We currently post actuals and open the forecast monthly.

Monthly for our data financial data. Most of the infrastructure data are uploaded monthly but some with less volatility e.g. Data Center, are uploaded quarterly.  

Monthly.  Prior month actuals are loaded as soon as they're available (generally available by the third business day of the month) and become the basis for the current month customer bill.

Thank you all for the quick responses. 

10 times based on new data being added

Actual (OpEx & CapEx) spend is loaded monthly (more in specific months if adjustments are made to the ledger after the regular load). In one previous company, I loaded actual spend for OpEx weekly, but pushed to Prod monthly.

Budget (OpEx & CapEx) is loaded once. In cases of a restate, budget is loaded again.

In a few past experiences, forecast is loaded in periods 3, 4, 6, 7, 8, and 9. Project forecast was more frequently completed, but not managed in any way by the TBMO nor loaded into TBMO tools.

For Cloud providers...it depends. In one case, we were loading daily as a means of supplementing the absence of a tool like Cloudability. In most cases, I expected a monthly refresh would be sufficient since a separate Cloud management tool (eg Cloudability) should be deployed.

Quarterly for now, but we are changing to a monthly cadence after the Q1 2020 loads are complete.

Kevin - is there a reason you were loading it quarterly? What was missing when you were following that cadence? 

Our data loads are done manually today, including the data extraction from our ERP. We chose the quarterly cadence mainly because of the manual effort involved. Now that we are close to automation, we are switching.

We load the GL actuals monthly but release the numbers quarterly

Infrastructure excluding virtual servers are loaded at the start of the quarter as there isn't much movement.

We also load forecast monthly

We load the GL monthly, but timesheet actuals are weekly and cloud billing is daily.

Monthly financial loads and updates to the IT infrastructure-related datasets (CMDB, etc.), including cloud invoices.

Daily updates to AWS consumption.

I've been trying to forecast for a couple of years now. Not much success so far due to lack of reliable metrics.

Finance do quarterly business reviews.

Monthly but it completely depends on cycle of your Actuals data re-freshness if its quarterly then there is no harm going with quarterly frequency.

Thank you all - this was very helpful. We are doing currently month, and we were rethinking, and wanted to see what others are doing.