• Skip to main content
  • Skip to footer
Revelwood Logo

Revelwood

Your SUPER-powered WP Engine Site

  • Who We Are
    • About Us
      • Our Company
      • Our Team
      • Partners
    • Careers
      • Join Our Team
  • What We Do
    • Solutions
      • Workday Adaptive Planning
      • IBM Planning Analytics
      • BlackLine
    • Services
      • Implementation Services
      • Customer Care
        • Help Desk
        • System Administration as a Service
      • Training
        • Workday Adaptive Planning Training
        • IBM Planning Analytics / TM1 Training
    • Products
      • DataMaestro
      • LightSpeed
      • IBM Planning Analytics Utilities
  • How We Help
    • Use Cases
    • Client Success Stories
  • How We Think
    • Knowledge Center
    • Events
    • News
  • Contact Us

Budgeting

IBM Planning Analytics Tips & Tricks: Cell Level Security Defaults

October 1, 2019 by Lee Lazarow Leave a Comment

Tips & Tricks

Did you know that you can have TM1 / Planning Analytics security always use your cell security definitions … even when the security definition cell is blank?

Values in a cell security cube override all other security. But if an intersection in the cell security cube is blank then, by default, other definitions such as cube, element and dimension security will be used.

In TM1 version 10.2, a new cube was created that allows you to override this approach. The cube is called }CubeSecurityProperties and it contains a setting called CELLSECURITYDEFAULTVALUE. The initial setting is blank, which allows the standard approach of “use the other definitions” to still apply.  However, you can change this approach by populating a value into the cube.

If you change the value in the }CubeSecurityProperties cube then all cells with an empty value in the cell security cube will use that setting. Values in the }CubeSecurityProperties cube can be set to NONE, READ or WRITE.

In the example below, blank cell security intersections will be set to READ

IBM Planning Analytics Tips & Tricks: Cell Security Defaults

When using this, be sure to think about any ripple effects associated with your existing security. For example, if you set a cube to READ then you will need to explicitly set cells to NONE that you don’t want users to see (whereas it may have already defaulted to NONE before the cube was populated).

This approach gives you more options to determine how cell security interacts with the rest of your security model.

IBM Planning Analytics, which TM1 is the engine for, is full of new features and functionality. Not sure where to start? Our team here at Revelwood can help. Contact us for more information at info@revelwood.com. And stay tuned for more Planning Analytics Tips & Tricks weekly in our Knowledge Center and in upcoming newsletters!

Read more IBM Planning Analytics Tips & Tricks:

IBM Planning Analytics Tips & Tricks: PA Modeling – The Settings Editor

IBM Planning Analytics Tips & Tricks: Creating Dynamic, Attractive Dashboards

IBM Planning Analytics Tips & Tricks: Preventative Maintenance to Maximize TM1 Performance

Home » Budgeting » Page 6

Filed Under: IBM Planning Analytics Tips & Tricks Tagged With: Analytics, Beyond Budgeting, Budgeting, Budgeting Planning & Forecasting, Financial Performance Management, IBM Cognos TM1, IBM Planning Analytics, Planning & Forecasting, Planning & Reporting, TM1

New Video Series: IBM Planning Analytics Tips & Tricks

September 24, 2019 by Lisa Minneci Leave a Comment

Tips & Tricks

Every Tuesday we publish written blog posts sharing IBM Planning Analytics Tips & Tricks from our PSG team. Today, we’re adding to our tips & tricks with a series of videos!

Watch this short video from FP&A Technology Director, Lee Lazarow, to learn what regions are, and how and why you’ll want to use them in Planning Analytics.

You’ll see and hear Lee explain:

  • Why regions are different from comments
  • How to create regions
  • How to shrink and expand regions

The best part about regions is that they enable quick and easy navigation!

IBM Planning Analytics, which TM1 is the engine for, is full of new features and functionality. Not sure where to start? Our team here at Revelwood can help. Contact us for more information at info@revelwood.com. And stay tuned for more Planning Analytics Tips & Tricks weekly in our Knowledge Center and in upcoming newsletters!

Home » Budgeting » Page 6

Filed Under: IBM Planning Analytics Tips & Tricks, Videos Tagged With: Analytics, Beyond Budgeting, Budgeting, Budgeting Planning & Forecasting, demo, Financial Performance Management, IBM Cognos TM1, IBM Planning Analytics, Planning & Forecasting, Planning & Reporting, TM1, video

Alternatives to Traditional Budgeting

September 20, 2019 by Brian Combs Leave a Comment

FP&A Done Right

Now that we have spent some time discussing several problems with traditional budgeting, let’s look at some alternate approaches. Here is a review of the first three problems from my prior blog:

  • Time Consuming and Costly
  • Quickly Irrelevant and Outdated
  • Financial Process Largely Disconnected from Specific Drivers

The biggest problem to me is the overall value (or lack thereof) that a traditional budgeting process provides the organization. The concept is sound. The execution is where the opportunity lies.

FP&A Done Right: Alternatives to Budgeting

One of the first steps is to determine the correct level at which to forecast. I’m referring to the number of accounts and entities (cost centers, profit centers, store fronts, functional areas, etc) you choose to budget. We often believe that more is more. In my experience, that is not true at all. Less is more. More detail means more time, not necessarily a better plan. There will always be puts and takes in your numbers as the year progresses and you compare actuals to budget. But if you build a very granular plan at the beginning, I have found that you end up with more misses. This is due to the budget review process where it is easy to look at the numbers through rose colored lenses. “The powers that be” make you bring every account or entity that is worse than prior year back to PY levels while keeping the goodness already baked in to other locations and accounts. You rarely get the offset so you end up with an unrealistic plan since we only take away one side of the equation.

Plan at the lowest level required for operational planning so you can get people, product, and capital in the right places at the right quantities. Your plan needs to be strategic in nature and should provide enough detail to allow for downstream capital planning. Don’t waste your time getting caught up in the weeds because the value add is simply to low. You must strike the right balance between detail and value to the company. As you spend time collecting numbers and assumptions for a given item, always ask yourself whether it provides actionable intelligence that will help you make meaningful decisions that drive the business forward.

As we learned in a prior blog, almost 50% of respondents stated that their business plan was outdated 1-3 months into the plan year. Wow!  Many of us spend several months on our plans only to have them become useless shortly after they are finalized. They become a variance column on our monthly reporting and then we just use it to see if we are on track for our bonus or not. If we agree that a business plan can still add value (which I do), then we need to find ways to shorten the amount of time it takes to complete.

One way that has multiple benefits is to make your budget driver-focused. Not only will this make the update process quicker, but it will help you connect your budget across all functions in your company. You need to ensure that your budget does not become a simple numbers game by aligning with operations, marketing, IT and others to build linkages throughout the organization, understand their needs for the upcoming year and create a shared vision that you are all marching towards. Choose the Key Performance Indicators (KPIs) that drive your industry and incorporate those into your planning process so you can quickly update your revenues and expenses. In my FP&A days, I focused on Rate per Day, Rate per Transaction, # of Transactions, # of Days, Transactions Per Employee, Average # of Vehicles, % of Revenue, etc. Armed with these assumptions, you can quickly update your budget when the need arises. Use these drivers to plan variable costs and then utilize a simple inflation factor to plan for your fixed costs. Here is a basic construct I have used successfully for many years:

(Rate * Driver) + Increment

The first part is clear. The increment is important because it provides the ability to plan for one-time items without having to artificially alter a rate to back in to the number. Without an increment or adjustment account, we lose the power of iteration as we can no longer simply update the driver because each rate needs to be reviewed as well to normalize it again for your starting point. Let’s say I have a particular expense that typically runs $100 (rate) per widget (driver). But I know that next month I have a one-time expense of $250 (increment). Using the above formula, I can easily increase my account by $250 to incorporate the one-time items. You can also use this to make last minute adjustments to your rate driven accounts without creating unrealistic rates.

While there are many changes you can make today that can help you avoid these pitfalls, we only had time to discuss a few here. We will look at a few more strategies in my next blog. As always, if you have some ideas to share or want to discuss further, please reach out.

Read more blog posts in Brian’s FP&A Done Right series:

FP&A Done Right: There is Life After December – The Fixed Forecast Dilemma

FP&A Done Right: Beware of Budgeting, Part I

FP&A Done Right: Beware of Budgeting, Part II

Home » Budgeting » Page 6

Filed Under: FP&A Done Right Tagged With: Analytics, Beyond Budgeting, Budgeting, Budgeting Planning & Forecasting, Financial Performance Management, FP&A, FP&A done right, Planning & Forecasting, Planning & Reporting

New Video Demo – Creating Dashboards in IBM Planning Analytics

September 18, 2019 by Lisa Minneci Leave a Comment

Video

In the third video of our series Creating a Cube in IBM Planning Analytics, Revelwood’s FP&A Technology Director, Lee Lazarow, demonstrates how to create a dashboard in IBM Planning Analytics. Watch this short video demo to learn how to create a dashboard from the sales cube built in the second video, using both a drag and drop methodology and Planning Analytics’ built-in wizard.

In this video, Lee demonstrates the results of sales commissions in the dashboard, as well as how to:

  • Change views
  • Create simplistic views of data for quick analysis
  • Visualize a set of numbers
  • Build different types of charts
  • Merge separate sets of data

Lee also demonstrates Planning Analytics’ built-in intelligence that shows which charts are best for your particular data.

Did you miss the first two videos in this series? Watch Creating Dimensions Planning Analytics and Creating a Cube in Planning Analytics.

Subscribe to our YouTube Channel and follow our playlist to watch the entire series How to Create a Cube in IBM Planning Analytics.

Home » Budgeting » Page 6

Filed Under: IBM Planning Analytics Tips & Tricks, Videos Tagged With: Analytics, Budgeting, Budgeting Planning & Forecasting, dashboarding, dashboards, Financial Performance Management, IBM Cognos TM1, IBM Planning Analytics, Planning & Forecasting, Planning & Reporting, TM1

IBM Planning Analytics Tips & Tricks: Blank Rows in Active Form Reports

September 17, 2019 by Lee Lazarow Leave a Comment

Tips & Tricks

Did you know when creating active form reports, you may sometimes want to separate sections? Some people like to create this separation via dashes or via bold line formatting. Some prefer to create “dummy” elements and use conditional formatting to make them appear like a blank line (although this approach is not recommended). Many clients, however, prefer to have the separation via a blank line.

Unfortunately, there is no easy way to create a blank line. We instead used a different approach with a client to create separation within rows in an Excel-based report.

Here is a sample report that we will start with, including the formatting range:

IBM Planning Analytics Tips & Tricks: Blank Rows in Active Form Reports

Column 1 references the element level of the account. This is the column that will be used for the formatting. The rest of the report is a standard active form. 

We now want to insert a blank area above the level 1 elements (e.g., above the line for Interest and above the line for Taxes).

Step 1: Insert a new column and edit the formatting for the applicable level

  • We will insert a new column to the left of the year
  • We will then format the new column for level 1 to have a very large font.  This report is currently set to use font size 11, so we will set this one cell to use font size 22.

Here is the new formatting area:

Blank Rows in Active Form Reports

Step 2: Within the report, hard code a value into the new column

  • Type the letter X into the new column. Remember that you only need to put the letter into the top row since Active Forms will replicate the value when you rebuild the report.

Here is the report after rebuilding it:

IBM Planning Analytics Tips: Blank Rows in Active Form Reports

There are now blank areas surrounding the rows associated with level 1, but the new formatting is only associated with the one column. 

Step 3: Hide the new column

  • In addition to hiding the column, you may choose to also manipulate the vertical cell alignment.

Once completed, here is the final report that users will see:

IBM Planning Analytics Tricks: Blank Rows in Active Form Reports

This approach uses formatting to create separation between rows within Excel. When combined with conditional formatting and other references in the first column (e.g. the format definition column), this approach can be both very powerful and very flexible.

IBM Planning Analytics, which TM1 is the engine for, is full of new features and functionality. Not sure where to start? Our team here at Revelwood can help. Contact us for more information at info@revelwood.com. And stay tuned for more Planning Analytics Tips & Tricks weekly in our Knowledge Center and in upcoming newsletters!

Learn more IBM Planning Analytics Tips & Tricks:

IBM Planning Analytics Tips & Tricks: The Ranked Report

IBM Planning Analytics Tips & Tricks: Snap Commands – Spelling

IBM Planning Analytics Tips & Tricks: Snap Commands – Sorting

Need more guidance? Take a look at our IBM Planning Analytics Training services and our Customer Care Program.

Home » Budgeting » Page 6

Filed Under: IBM Planning Analytics Tips & Tricks Tagged With: Analytics, Budgeting, Budgeting Planning & Forecasting, Financial Performance Management, IBM Planning Analytics, Planning & Reporting, TM1

IBM Planning Analytics Tips & Tricks: Cellput vs CellIncrement

August 27, 2019 by Lee Lazarow Leave a Comment

Tips & Tricks

Did you know one of the most popular uses of TurboIntegrator is to load data into a cube? There are many different commands that can be used to load data depending on whether the data consists of numbers, strings or attributes.

When loading numeric data, there are two approaches that can be followed. 

  • One approach is to load the value from the record into Planning Analytics using the CellPutN command. This approach will overwrite any existing data in the cube.
  • One approach is to accumulate the value from the record with any existing data in the cube.

The purpose of this write up is to discuss how to accumulate data in a Planning Analytics cube. 

There are two approaches to accumulating data. The first approach is to get the data that is already in the cube, add that value to the value from the record, and then reload the total into TM1. Here is an example of this using a cube called ‘Finance’:

numExisting = CELLGETN ( ‘Finance’, vVersion, vPeriod, ‘Amount’);
numTotal = numExisting + vValue;
CELLPUTN ( numTotal, ‘Finance’, vVersion, vPeriod, ‘Amount’);

This approach creates temporary variables to tell you the existing amount and the new total. The benefit to this approach is that you can easily do error checks if the results don’t reconcile to your expected results.  However, the disadvantage of this approach is that you had to write multiple lines of code to perform one function.

You can consolidate these lines by using a single command called CellIncrementN. The increment command increases the existing value by the value from the record. Here is an example of this using the same cube:

CELLINCREMENTN( vValue, ‘Finance’, vVersion, vPeriod, ‘Amount’);

If the data loads properly then we have shortened our script by only having to create one line of code. However, if the data did not load properly then we have done this at the expense of not being able to easily reconcile the pieces.

There are multiple commands that can be used to load data into a cube, each of which has its own pros and cons. 

IBM Planning Analytics, which TM1 is the engine for, is full of new features and functionality. Not sure where to start? Our team here at Revelwood can help. Contact us for more information at info@revelwood.com. And stay tuned for more Planning Analytics Tips & Tricks weekly in our Knowledge Center and in upcoming newsletters!

Learn more IBM Planning Analytics Tips & Tricks:

IBM Planning Analytics Tips & Tricks: Clearing all Data from a Cube

IBM Planning Analytics Tips & Tricks: IFERROR

IBM Planning Analytics Tips & Tricks: Rule Concepts That are Often Forgotten

Need more guidance? Take a look at our IBM Planning Analytics Training services and our Customer Care Program.

Home » Budgeting » Page 6

Filed Under: IBM Planning Analytics Tips & Tricks Tagged With: Budgeting, Budgeting Planning & Forecasting, Financial Performance Management, IBM Planning Analytics, Planning & Reporting, TM1

IBM Planning Analytics Tips & Tricks: Errors in Non-writeable Cells

August 20, 2019 by Lee Lazarow Leave a Comment

Tips & Tricks

Did you know IBM Planning Analytics is smart enough to look at the write permissions of a cell before attempting to load values into a cube? Have you ever tried to run a load process and then receive errors stating that you cannot write data to a cell? While Planning Analytics is ensuring that your data load is properly working, the errors can be disconcerting and can make the load process appear unstable.

TurboIntegrator contains a command called CellIsUpdateable that can be used to check the write permissions of a cell before attempting to load data.  The command uses the same parameters of the various CellGet functions and results in a value of 1 or 0 where 1 means the cell can be written to and 0 means the cell cannot be written to.

CellIsUpdateable(Cube, Dim1, Dim2, … )

This formula is often used in conjunction with an IF statement to determine whether a CellPut command should be used. Here is an example of using the commands within a Turbo Integrator script:

# Define cube name
strCube = ‘Finance’;
# Only load data if the cell is updateable
IF ( CELLISUPDATEABLE(strCube, ‘Budget’, ‘Company1’, ‘Jan 2019’, ‘Amount’) = 1);
     CELLPUTN (vValue, strCube, ‘Budget’, ‘Company1’, ‘Jan 2019’, ‘Amount’);
ENDIF;

This concept can be extended to include error messages, ItemSkip commands, or other aspects of an ELSE component. But most importantly to your end user … no error will appear when trying to load data that should not be loaded.

Error messages are great for developers and great for data reconciliation, but it’s not always what you want your users to see. This approach helps limit the messages that appear to the user.

IBM Planning Analytics, which TM1 is the engine for, is full of new features and functionality. Not sure where to start? Our team here at Revelwood can help. Contact us for more information at info@revelwood.com. And stay tuned for more Planning Analytics Tips & Tricks weekly in our Knowledge Center and in upcoming newsletters!

Learn more IBM Planning Analytics Tips & Tricks:

IBM Planning Analytics Tips & Tricks: Rule Concepts that are Often Forgotten

IBM Planning Analytics Tips & Tricks: How to Manipulate Case Used for Text

IBM Planning Analytics Tips & Tricks: Clearing all Data from a Cube

Need more guidance? Take a look at our IBM Planning Analytics Training services and our Customer Care Program.

Home » Budgeting » Page 6

Filed Under: IBM Planning Analytics Tips & Tricks Tagged With: Budgeting, Budgeting Planning & Forecasting, Financial Performance Management, IBM Planning Analytics, Planning & Reporting, TM1

IBM Planning Analytics Tips & Tricks: Clearing All Data from a Cube

August 13, 2019 by Lee Lazarow Leave a Comment

Tips & Tricks

Did you know there may be several situations during development where you may want to clear all of the data from a specific cube? This could be due to a new process to reload data, a second round of user testing, or a migration from DEV to PROD. 

There are a few approaches that can be used to clear data from a cube.  One approach is to create of a view which consists of the entire cube and using then performing a ViewZeroOut against that view. This can be done via the following script:

# Define cube name

strCube = ‘Finance’;

# Destroy any existing views and recreate a new one

IF (VIEWEXISTS (strCube, strView) <> 0);

VIEWDESTROY (strCube, strView);

ENDIF;

VIEWCREATE (strCube, strView);

# Perform Zero Out

VIEWZEROOUT (strCube, strView);

The benefit to this approach is that you now have flexibility to manipulate your view. You can have the view filter to specific elements within a dimension and/or set the view to ignore values such as rule-based values.

Another approach is to use the CubeClearData command. The CubeClearData command clears all data within a cube. Using this function is faster than writing a script at the expense of using an “all or nothing” approach. The same process defined above can be written using the following single line:

# Define cube name

strCube = ‘Finance’;

# Clear all data from the cube

CUBECLEARDATA (strCube);

Note that the CubeClearData command also clears any cells in the cube that are fed with feeders. If you want to restore the fed cells then you must either manually resave the rule that establishes the feeders or use the CubeProcessFeeders function.

There are multiple ways that can be used to clear data from a cube and you can define what approach is best for you.

IBM Planning Analytics, which TM1 is the engine for, is full of new features and functionality. Not sure where to start? Our team here at Revelwood can help. Contact us for more information at info@revelwood.com. And stay tuned for more Planning Analytics Tips & Tricks weekly in our Knowledge Center and in upcoming newsletters!

Learn more IBM Planning Analytics Tips & Tricks:

IBM Planning Analytics Tips & Tricks: Creating Selectors in Planning Analytics Workspace

IBM Planning Analytics Tips & Tricks: Creating Buttons in Planning Analytics Workspace

IBM Planning Analytics Tips & Tricks: Synchronizing Selectors in Planning Analytics Workspace

Need more guidance? Take a look at our IBM Planning Analytics Training services and our Customer Care Program.

 

Home » Budgeting » Page 6

Filed Under: IBM Planning Analytics Tips & Tricks Tagged With: Analytics, Budgeting, Budgeting Planning & Forecasting, Financial Performance Management, IBM Planning Analytics, Planning & Reporting, TM1

FP&A Done Right: Beware of Budgeting – Part II

August 9, 2019 by Brian Combs Leave a Comment

FP&A Done Right

How is your budget/budget prep coming along? Have you set aside time to rethink your process? In that last installment of FP&A Done Right, we started our enumeration of the problems with traditional budgeting. Before I discuss several more, here is a reminder of the last few problems:

  • Time consuming and costly
  • Quickly irrelevant and outdated
  • Financial process largely disconnected from specific drivers

Let me highlight more now and then we will move towards some alternative approaches.

Principled upon negotiating/gamesmanship

I can still remember my first visit to Corporate to review (or as I soon learned, to defend) our annual budget. Back then, I was fresh off my MBA and I had landed a job at one of our Region offices. We had just spent months building a plan from the lowest level, capturing input and feedback from every location manager and painstakingly describing every variance to the penny. We were ready. This was a done deal. Boy was I naïve. We were escorted into a nice room with a large table. Around the table I could see the president of our division and the heads of every major functional area ready to discuss our plan. Game on! My controller and I didn’t even get a chance to pull out most of the backup schedules we had created. He spent his time trying to negotiate fewer expense reductions and less revenue while I was busy taking notes on all the “savings” and “initiatives” the team had just found for us during the review. Great news. Thanks for the assist. I learned my lesson that day. After that, I knew that I had to pad my expenses and sandbag my revenue. They knew we did it too which is why they had us take a 5-10% cut in expenses as soon as we walked in the door. That is a difficult game to stop playing and, in the end, no one wins. Yet, many of us continue to play.

Triggers Unnecessary Spending

Since our budget numbers are frequently tied to prior year spend rather than being based on needs (a zero-based budgeting approach), we feel the need to spend money just so we have the same amount available to us next year. This is crazy, but I still see it today. We should be creating an environment where our front-line managers are rewarded for being fiscally conservative, not penalized. If you find a way to save money this year, we should be analyzing what you did so we can replicate it with your peers rather than giving you a hard time next year since you now have a large YoY increase.

Creates an inflexible performance contract

This is a big one as it impacts your managers directly in their bank accounts. This is especially true when incentives are tied to performance against the annual business plan. Once my budget was completed, I knew I would spend the rest of the year running actuals vs budget reports so we could determine what our bonus would be. If you remember from the first part of this blog, almost two-thirds of budgets are outdated between 4-6 months into the plan. If that’s the case, why are we using that number to determine the bonus for our managers? I want to reward my managers for changing course if they see something that is in the way of them achieving their goals. Compensate them based on what is occurring now, not what you thought was going to happen 12 months ago. When we focus on an inflexible budget number, we begin to manage to that number.  Don’t fall in to that trap.

Drives Wrong Behavior

It doesn’t take long before you know roughly where the year will pan out vs the budget. You know fairly quickly whether it is attainable or a long shot.  Since compensation is tied to the budget, it tends to drive the wrong behavior. You should expect your managers to do what is in their best interest. It is your job to ensure that by doing so, the company gains as well. If I am in the back half of the year and I already know I can’t achieve my annual budget numbers, where is the incentive for me to continue to find cost savings and improve my processes. I might as well give up on trying to get better this year because I won’t reach my bonus threshold anyway.  Right? Maybe I’ll push off a cost savings initiative until next year.  Or I’ll try that new revenue generating idea at the start of next year. The same is true if you have already maxed your bonus for the year. Why continue to do better? Save some of that goodness for next year. You need to make sure that the company goals are aligned with the individual goals. A budget can create a false sense of security and it may be holding the organization back from achieving its true potential.

It’s often easier to ‘see’ a problem when someone else describes it. My hope is that while reading this, you took some time to compare and contrast these issues with your methodology and approach to the budget. Does anything look familiar to you? If so, perhaps it is time to make a change.  Please reach out and share your stories with me. In my next blog, we’ll discuss some alternatives to these problems that you can begin using immediately.  Happy budgeting!

Read more posts in Brian’s FP&A Done Right Series:

FP&A Done Right: Beware of Budgeting, Part I

FP&A Done Right: The Importance of Including FP&A Often and Early in Your Strategic Planning Process

FP&A Done Right: 5 Signs it’s Time to Rethink Your Process

Home » Budgeting » Page 6

Filed Under: FP&A Done Right Tagged With: Analytics, Beyond Budgeting, Budgeting, Budgeting Planning & Forecasting, Financial Performance Management, FP&A, FP&A done right, Planning & Forecasting, Planning & Reporting

  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 4
  • Page 5
  • Page 6
  • Page 7
  • Page 8
  • Interim pages omitted …
  • Page 19
  • Go to Next Page »

Footer

Revelwood Overview

Revelwood helps finance organizations close, consolidate, plan, monitor and analyze business performance. As experts in solutions for the Office of Finance, we partner with best-in-breed software companies by applying best practices guidance and our pre-configured applications to help businesses achieve their full potential.

EXPERTISE

  • Workday Adaptive Planning
  • IBM Planning Analytics
  • BlackLine

ABOUT

  • Who We Are
  • What We Do
  • How We Help
  • How We Think
  • Privacy

CONNECT

World Headquarters

Florham Park, NJ | 201 984 3030

European Headquarters

London & Edinburgh | +44 (0)131 240 3866

Latin America Office

Miami, FL | 201 987 4198

Email
info@revelwood.com

Copyright © 2025 · Revelwood Inc. All rights reserved. Revelwood® and the Revelwood logo are registered marks of Revelwood Inc.