The Answer Series: Is Budgeting at a High Level a Best Practice?

The Answer Series: Is Budgeting at a High Level a Best Practice?

I receive questions all the time from people looking for a best practice or simply to answer a pressing question. One that has come up (a lot) recently is “What is the best level to budget at?” The debate being centered on budgeting/planning at a low or high level. Here is my answer:

Budget at the same level you’ll capture your actuals in – but make it easy.

Here's The Context

There are two reasons why this question tends to come up. The first is that some consulting firms have advocated for budgeting at a summary level (I’ll explain why) and the other is some Budgeting/Planning FP&A software vendors discourage budgeting at a detailed level (I’ll explain that too).

The fundamental argument put forth for budgeting at a summary level is a pretty simple one. “It’s easier.” I’ll detail later why that is not true, but that’s the rationale in a nutshell. Beyond that, advocates for budgeting at a high level or summary level talk about “materiality”. As in “Does it really matter if it’s Airfare expense or Hotel expense? It’s all Travel expense, don’t get lost in the weeds, it’s not material.” That can sound smart, but we’ll see the trap that puts you in.

Is High Level Budgeting Really Easier?

I’m going to use an illustration focusing on Operating Expenses (since every reader should be able to relate to that) but the same arguments and analysis hold equally true for Sales & Revenue, CapEx, Cost of Goods Sold (COGs) and every other element of the P&L.

If your company has 100 general ledger accounts for Operating Expenses, and the budget template only calls for 20 lines to be budgeted, on paper that would appear to be easier. In fact I’ve heard from some Finance teams that took this approach that they believed they’d be heralded as heroes “for eliminating all that work.”

The problem with this approach is it introduces a fundamental disconnect between how the business is budgeted, and how the business is run. That ultimately creates more work, not less.

Here’s a simple illustration. I’m a Cost Center Manager with a $1MM budget. If I’m expected to manage to that budget I need to understand how my Actual expenses are coming in and how they’re tracking with what I Budgeted. If there is a mismatch between the two that makes my life harder. And it’s actually the detail that helps me understand what’s happening in the business and manage it.

For example, if the General Ledger Accounts related to Travel include Lodging, Airfare, Meals, Ground Transportation and Miscellaneous; then knowing which of those accounts a variance is coming from will help me manage my business. For example, if most of a $25K variance is in Airfare and we’re in the middle of an oil crisis with airfares rising every day, that’s one thing. If on the other hand 95% of the $25K variance is coming from Miscellaneous, then I have a very different issue on my hands.

Here's the problem. If my budget is only at the summary level “Travel” I really have very little visibility into the variance, and that makes it that difficult to explain or manage. I need someone to start pulling invoices and cobbling together a picture of the spending, then start talking with my managers about it and see if I can come up with an explanation.

You’ve actually made my job harder by not allowing me to budget at the same level the Actual results come in at.

Now this is where someone might say, “Hold on. Who said anything about not allowing people to budget at a lower level, they’re free to do so if they want.”

That creates more work for budget holders as well, here's why. If the corporate template (e.g., “Travel”) is at a higher level than the G/L Accounts and the way a department wants to manage the business (Lodging, Airfare, Meals, Ground Transportation and Miscellaneous) then that department needs to create their own template. Then they need to summarize the budget detail in order to populate the Corporate template… and make certain the two templates tie out. That's more work, not less.

There's also the recurring problem of Reporting Actual Expenses versus Budgeted Expenses.

It’s very common for the Finance department to produce a financial report for each Cost Center comparing Actual spending to Budgeted spending. This normally comes right out of the financial reporting system. The problem is if actuals come in at a detailed G/L level and the budget in the reporting system has been captured at a summary level, then there is a fundamental mismatch and therefore the business value of this crucial monthly report is greatly reduced -- and possibly even negated.

The Not So Hidden Role of Software Vendors

FP&A Software vendors may encourage budgeting at a summary level because it’s easier to implement, and because they are often working in concert with management consultants who advocate this approach.

Another common reason why at least some FP&A Software vendors may push to budget at a summary level is that creating budget templates… binding them together through relationships… and tailoring them to accommodate needs of different business units, divisions or functional areas, often requires custom coding and scripting. That can get expensive. Knowing this, they may choose to discourage budgeting at a detailed level to keep implementation costs down.

Regrettably, this often results in a
“one-size -fits-nobody” template that forces budget holders right back to excel.

The Key – Make It Easy

Here’s a simple solution. Make it easy for a budget holder to budget at a detailed level OR high level and automatically synch the two. If you’re still budgeting in Excel, that last sentence may conjure up this image in your mind:

No alt text provided for this image

Let me get technical for just a moment, since the solution is technical (at least in part). The solution requires what is known as a reverse algorithm. This enables you to overcome the CIRC REF! error you may see if you’re still using Excel for budgeting. The reverse algorithm allows you to enter data in a template and have it cascade down automatically to the lowest level OR budget at the lowest level and roll it up automatically – or budget at any level in between. Really.

The benefit is everyone gets what they want. The team in Corporate Finance that cares only about a summary level budget gets what they want, and the budget holders who want (and need) the details to manage the business get what they want.

Another part of “making it easy” means replacing coding and scripting with drag ‘n drop configuration. If it’s overly complicated to create screens and templates for multiple business units or functional areas (because they all need special coding and scripting), then it simply won’t happen. On the other hand... if a non-technical person can leverage drag ‘n drop configuration, then getting people what they want and need becomes a whole lot easier.

So for all the reasons discussed here, the real answer to the question "What level should we be budgeting at" is "Budget at the level you capture Actuals in."

For a quick summary For and Against budgeting at a summary level you can refer to the table below:

No alt text provided for this image

Do you have a suggestion for The Answer Series? If so you can add them below or find me here.

Anastasia CHEN, FPAC, CPA

EMBA'25 Candidate | Business Performance Analyst | Strategic Analysis

3 年

When the inputs are garbage, shall we focus on fixing the inputs; or, fixing the process to make garbage inputs work?

回复
Travis Linneweber

Budget Director and Higher Ed Finance Fan

3 年

Interesting article. Thanks for sharing. This has me thinking about ways to encourage "accountability" and "ownership" of the budget at different levels of the organizational structure.

回复

Hello Lawrence, besides reverse algorithm, it appears one would still need some sort of hierarchical reconciliation to address the "level" issue in order to switch between high level and detailed ?

要查看或添加评论,请登录

Lawrence Serven的更多文章

  • Don’t Get Stuck in the Middle Seat

    Don’t Get Stuck in the Middle Seat

    …When buying software for your company "They're all the same" It's hard to imagine -- since more people have flown on…

    1 条评论
  • USING AI FOR BUDGETING

    USING AI FOR BUDGETING

    AI is extremely promising technology, but can we use it to make the budgeting process more efficient – and more…

    2 条评论
  • How to Become a GREAT Finance Business Partner

    How to Become a GREAT Finance Business Partner

    Presuming you are in a Finance Business Partner role (or want to be) how does someone develop their A Game? How do you…

    1 条评论
  • AI: The #1 Shortcoming Every CEO Should Know

    AI: The #1 Shortcoming Every CEO Should Know

    The promise of AI is enormous, and what it’s already delivered is groundbreaking. As Arthur C.

    4 条评论
  • Using ChatGPT to write Excel formulas

    Using ChatGPT to write Excel formulas

    Ever felt puzzled writing Microsoft Excel formulas? ChatGPT can do the hard work for you. I came across an interesting…

  • 2023 Scenario Planning at Google

    2023 Scenario Planning at Google

    How is Google – one of the leading global tech companies known for its world-class innovation and execution, preparing…

  • The Problem With Your Cash Flow Isn’t What You Think It Is

    The Problem With Your Cash Flow Isn’t What You Think It Is

    On occasion I’ll run across an article I think is worth reading but realize you might not have time to read the entire…

  • 7 Deadly Mistakes Buying B2B Software

    7 Deadly Mistakes Buying B2B Software

    “Experience is a great teacher, but smart people learn from others' experience.” Abraham Lincoln Having worked…

    1 条评论
  • Analytics Isn't for Analysts

    Analytics Isn't for Analysts

    A colleague sent me a thought provoking post I had to share. It’s written by the very talented and insightful Anna…

  • HOW THE SUPPLY CHAIN WENT OFF THE RAILS

    HOW THE SUPPLY CHAIN WENT OFF THE RAILS

    Seems like “Supply Chain” and “Inflation” occupy more headlines today than they have in decades. Why is that? How did…

    2 条评论

社区洞察

其他会员也浏览了