Tips for mastering financial modelling of balance sheets

09 January, 2010

The Balance Sheet can be one of the trickiest financial statements to model, as several line items are the result of decisions you make for the other financial statements. Most importantly, getting your balance sheet to balance (and stay balanced!) can be quite a challenge.

Here are a few tips to help you master the balance sheet:

  • As with any financial model, ensure the line items in your balance sheet are linked to other areas of the model.  As tempting as it may seem, never enter hard-coded numbers!  For example, depreciation can be calculated elsewhere and pulled through to the balance sheet.
  • Resist the urge to “cheat” and add in dummy numbers.  It may seem appealing when you’re tearing your hair out at 2am, but it’s not good practice and you’ll regret it later.
  • Leave finalising your balance sheet numbers to the end of the modelling process.  By all means build the structure of the balance sheet first, but wait until the rest of your model is near completion before attempting to balance your balance sheet.
  • Don’t be afraid to add hidden rows.  If your model is reasonably complex, you’ll probably need more than one row to calculate “Cash at bank”, for example.
  • The use of in-built error checks can alert the user when the balance sheet does not balance.  Your balance sheet might balance now, but make a few structural changes to another part of your model, and it suddenly doesn’t balance anymore!  An error check or use of the live watch window can help keep an eye on this.
  • Create a “forecast” balance sheet aligned with your model.  For example if your model shows five year projections, your investors will want to know what the balance sheet will look like in five years.
  • Unlike the P&L which shows revenue and expenses relevant to each period, a balance sheet shows a snap-shot of what the company owns and what it owes at the end of each year.  As basic as it may sound, don’t forget to roll your assets across each year.

How to link the balance sheet to profit and loss and cashflow statement

When modelling your balance sheet, use the following guidelines to help you determine how each line item should be either linked to another financial statement directly, or determined through the creation of an assumption.

  • Accounts Receivable can be calculated using revenue and collections expectations.  It can be derived from the formula revenue / 365 * debtor days.
  • Accounts Payable can similarly be calculated using operating expenses (opex) using the formula opex / 365 * creditor days.
  • If you are modelling inventory, it can be calculated based on initial purchases, plus additions to inventory, minus cost of goods sold.
  • Non-current Assets will come from your depreciation schedule, where you have calculated capital purchases and their depreciation.  This will be driven by assumptions about fixed assets per employee and other company needs.
  • Short Term Loans typically cover short term cash needs, which may be driven from the Cash Flow Statement.
  • Long Term Loans are used to cover long term funding needs, often in lieu of raising capital.  An assessment of your start-up and short term needs will help determine the amount.
  • Retained Earnings is an accumulation of your Net Income from the Profit & Loss prior to the current period.
  • As the name suggests, a balance sheet MUST balance when completed i.e. Assets = Liabilities + Equity.

Comments

   Hi  ,

  i am so happy to join the finance modelling site .

 

  regards

  MCG

 

 

Submitted by mpoubou constel (not verified) on Wed, 27/01/2010 - 01:08.

Hi,

I'm quite surprised at the third bullet point down. I would suggest that a balance sheet should be built into the model from the start, and that as each line item in the model is built in (e.g. revenue, costs, debt etc) the balance sheet is updated. This avoids having a big exercise at the end of the model build to try to create a balance sheet and then get it to balance. At this time there may be numerous problems with the underlying coding which net off to a single 'balance sheet difference', leading to the 'tearing your hair out at 2am' scenario to which you refer.....

Would be interested to hear the argument for the approach you suggest.

Tom

Submitted by Tom (not verified) on Thu, 11/03/2010 - 00:25.

Hi Tom,

I see your point and if you build the structure of the model first, and then populate it with numbers afterwards, then yes, you could build the balance sheet before finalising the rest of the model.  Normally though, you don't know exactly where in your model the revenue, costs, cash etc will be located until you are near competion.  The structure of the model is usually an iterative process right until the end. 

Danielle.

Submitted by danielle on Thu, 11/03/2010 - 09:49.

To me, I leave the balance sheet until last (as in I build the framework but leave linking any formulas until last) because all of the Bal Sheet numbers are derived from the other 2 financials and assumptions, and like Danielle stated I wouldn't know exactly where to link to until those are done.  It's a bit more of an art than science for me at the beginning for sure!

Submitted by Chris Benjamin (not verified) on Thu, 11/03/2010 - 11:12.

Danielle,

I would be interested to see an example of one of your models that contains the three primary financial statements. Do you have one that I could take a look at please?

Thanks

Tom

Submitted by Tom (not verified) on Fri, 19/03/2010 - 23:50.

Hmm, I don't have anything non-confidential I can publish.  There are a number of Excel templates that can be downloaded though at http://www.vertex42.com/

Submitted by danielle on Tue, 30/03/2010 - 12:44.

I've just come across an interesting discussion on Finance 3.0 which also talks about Financial Modelling with Balance sheets and the order in which you should build them.

http://www.finance30.com/forum/topics/projected-balance-sheet

Enjoy!

Submitted by danielle on Wed, 31/03/2010 - 20:40.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd><img><h1><h2><h3><p><br>
  • Lines and paragraphs break automatically.
  • Images can be added to this post.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
2 + 7 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.